-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with SWI #7
Comments
The most serious technical shortcoming of SWI is described in SWI-Prolog/roadmap#14. Other technical issues are:
|
Further items:
The original library(clpfd) in SWI was tested 100+ CPU-years under the assumption that the underlying implementation does not change. That assumption turned out to be very wrong. Extensive tests cannot be manually inspected (even fast computers need years to wade through them), the errors specified in the standard are thus extremely helpful to judge the situation automatically and sort out false positives. |
@UWN Why would porting clpz to SWI require ISO conformance? I understand that ISO conformance has certain benefits in itself, but I do not see the clpz-specific part there. |
@wouterbeek A reliable porting procedure requires testing. And that's where ISO conformance comes into play (see above post) - in particular precise errors but also the abstract syntax. SWI's actual unification mechanism implementation below is far too idiosyncratic to be a sufficient condition for a successful port. |
Additional reasons are mentioned in #4. Since you have also contributed to the web page, I hope you can eliminate some of these problems, ensuring that CLP(FD) is presented in the way it is intended. This was previously the case, but is no longer the case with the new web page. |
any progress on this issue since 2017? |
If this cannot be done ATM because of missing libraries or open issues, then we can at least assemble a list of requirements SWI should meet in order to add compatibility in the future.
The text was updated successfully, but these errors were encountered: