Changes Introduced in Version 3.8.2

Version 3.8.2 is a bugfix release only, no new features has been added.

• call_residue/2: fix bug when the goal called copy_term/2.
• listing/[1,2], portray_clause/[1,2], top-level: cope with constrained/attributed variables.
• portray_clause/[1,2], write_term/[2,3] with indented(true): do not juggle module prefixes.
• Foreign resources: problems with prelinked resources and with clpfd
• Foreign resources: The returned arguments from a foreign function are now properly ignored if an exception was raised with SP_raise_exception().
• Foreign resources: Added some, for now, undocumented callbacks to <sicstus/sicstus.h>. Documented SP_to_os(), SP_from_os().
• Atom garbage collector: don't reclaim undefined predicates that have pointers to them; some atom locations were not traced.
• Local stack shifter bug.
• Source info management: ensure expansion of the compiled file table.
• Backtracking from fastcode to compactcode special case.
• Bytecode relocation bug after restore.
• Compiler bug on very large clauses.
• SP_WcxOpenHook: incorrect prototype.
• Emulator kernel: performance bugs.
• 64-bit portability bugs.
• library(bdb): a relative filename given in db_open/5 was treated by SICStus as relative to the current working directory, but should be relative to the given BDB environment.
• library(clpfd): somewhat faster arithmetic, lingering bugs in serialized/[2,3] and cumulative/[4,5], labeling/2 options value/1, variable/1
• The configure script did not specify the correct Irix/MIPS ABI/ISA level building with GCC.
• Added --with=<package> options to spld and splfr to override default installation path for third-party software packages.
• spld: Fixed bugs in argument handling. .pl file arguments are no longer compiled at spld time, but passed directly to SP_load().
• library(jasper): Multiple threads are allowed to call SICStus without IllegalCallerException being thrown. See Java Threads.
• library(jasper): Argument-checking bug in jasper_call_static/6 and jasper_call_instance/6.
• Recover properly from memory allocation failures.