Markus Triska
Markus Triska
@pmikkelsen: I found another issue where rustyline is mentioned: https://github.com/mthom/scryer-prolog/issues/1897 Is this related, and can it be addressed analogously?
Yes indeed, `PipeReader` could be fitting! I would greatly appreciate if you could take a look also at this conceptually related issue in case you are interested, thank you a...
Yes, thank you!
In my opinion, `use_module/1` should require a proper module. You can still easily consult the file also in Scryer Prolog even without a module declaration, by specifying it on the...
The **`include/1`** directive would be useful to implement this, I have filed #634 for it. Please note that it ought *not* to be necessary to recognize any specific Prolog implementation...
Regarding the preprocessor: As is, this is very limited in practice, because it cannot be used *within* Prolog terms, and that is often required in practice. For instance, suppose a...
I have a similar experience with supporting different versions of OpenSSL in code. In my experience, at least one important takeaway is to test for **features** instead of specific systems...
Also with infix operators, we found this thanks to #3062: ?- X = .. + .. . X = .. + ..., unexpected.
Also with prefix operator: ?- X = + .. . X = + ..., unexpected.
@constraintAutomaton, @bakaq: What do you think about adding a more comprehensive **`info`** manual for Scryer, and mentioning that in the `-h` output? I think you @jjtolton at one point already...