Jan Wielemaker

Since many years there is a vision in hardware land that ultimately we will get uniform non-volatile memory instead of various layers of fast volatile memory connected to slow persistent...

Oh, it can. AFAIK, such systems have existed. Right now the route is probably to connect to external or embedded database technology. From their you can make the data available...

On 08/06/2014 07:34 AM, Miriam Zusin wrote: > I did not realize that this version is so old :) > With the new version I get the following error: >...

Not sure, but you may have to recompile the C# binding. The SWI-Prolog API is often not binary compatible between major versions. It is usually source code compatible. Another possible...

There is little choice given the one-direction HTTP protocol. So, if you get a server response, it may either be a binding or output (or destroy, ...) You can handle...

Might be better to check on SWI-Prolog's Discourse platform. Please also include the Windows version. I have no clue except that for most people this doesn't seem to be an...

Might be related to arm64? If the JVM is arm64 you probably also need an arm64 version of swi-prolog. We do not provide binaries for this. Quite likely they can...

Might be better to ask on the Discourse forum. I can barely belief such elementary code can show a bug. It is probably more misunderstanding of CHR. I'm not an...

This issue has been mentioned on **SWI-Prolog**. There might be relevant details there: https://swi-prolog.discourse.group/t/a-strange-behavior-of-chr-package/4964/1

All I can say is that, unless someone redefined I/O, write/1 writes to `user_output`, which is initially bound to `stdout`. This is a line-buffered stream, so to see something you...