... SICStus^1.1

In XSB, we try to keep the implementation of attributed variables to be compatible with SICStus.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... next.^1.2

XSB does not convert pipes into I/O ports automatically. Because of the way XSB I/O ports are represented, they are not inherited by the child process and they do not make sense to the child process (especially if the child is not another xsb). Therefore, we must pass the child processes an OS file descriptor instead. The child then converts these descriptor into XSB I/O ports.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... compiled.^2.1

Please see the special instructions for Windows.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... characters).^6.1

The string feature will be deprecated when XSB will have working atom garbage collection. When URL is a list of characters, then Result is also a list of characters, which eases the burden on the atom table and allows XSB to work longer before memory is exhausted.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... request^7.1

e-mail xsb-contact@cs.sunysb.edu

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.