-
Notifications
You must be signed in to change notification settings - Fork 139
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
Porting library(diadem) to Scryer Prolog #840
Comments
I'm pretty sure |
triska
added a commit
to triska/scryer-prolog
that referenced
this issue
Feb 28, 2021
Ah yes, thank you a lot! |
triska
added a commit
to triska/scryer-prolog
that referenced
this issue
Feb 28, 2021
$ scryer-prolog -f diadem.pl ?- "caenum" = "caelum".?X. thread 'main' panicked at 'Out of bounds access', src/machine/compile.rs:1666:41 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Update: The crash is now resolved. |
mthom
added a commit
that referenced
this issue
Dec 18, 2023
Thank you, I have updated the initial description with the current state of the issue: ?- "caenum" = "caelum".?X. error(existence_error(procedure,'$free_variable_set'/3),'$free_variable_set'/3). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to port Ulrich Neumerkel's
library(diadem)
to Scryer Prolog for declarative debugging. The current state of the port is in thediadem
branch at:https://github.com/triska/scryer-prolog/tree/diadem
See specifically
diadem.pl
for the source.So far, loading the library works:
However, trying the example from the source file, I get:Why?(Update: resolved by adding alimes/4
is defined in the file, so this should work.meta_predicate/1
declaration)Update:
The current state of the issue is:
@UWN: Could you please advise what is needed here, and what should be added to Scryer Prolog to emulate
'$free_variable_set'/3
in a conforming system?I see also that
numbervars/4
is used by the library, should that be added to Scryer Prolog or is it possible to solve this differently?The text was updated successfully, but these errors were encountered: