Markus Triska
Markus Triska
?- write_term("ab", [max_depth(1)]). [a,b] true, unexpected.
Interesting, I would say that this is an unexpected error! The expected error and toplevel answer when interrupting a computation with Ctrl-c is: error('$interrupt_thrown',repl/0).
Also: ?- "\x0\\x0\" = [_,_]. false, unexpected. true. % expected
This issue may be confined to *parsing* strings, at least the following works exactly as expected: ?- A = '\x0\\x0\', atom_chars(A, Cs), Cs = [_,_]. A = '\x0\\x0\', Cs =...
Very nice work Douglas! Before continuing with this, please let us make sure that what we already have is as robust as possible. For example, today I found another issues...
The point is that _after_ the unification of two variables, only a single variable remains, so it also makes sense that users only have to update the attributes of **one**...
I managed to get the drawing of the BDD working from "normal" `sat/1` residuals, using the new `varsnumbers_names/3`. Please see the [repository](https://github.com/triska/swish/commits/master). However, I still need a way for users...
Is there any way to make the `clpb_residuals` flag work like on the normal Prolog toplevel also in SWISH? If that is possible, I would strongly prefer this over other...
I think the last route is best, also for future uses. Please do think about this. I will also think about the extension approach. Currently, I have severe doubts about...
Could you please post the content of the buffer `*ediprolog-history*`? Thank you a lot!