tests/accumulator/*.m:
tests/analysis_*/*.m:
tests/benchmarks*/*.m:
tests/debugger*/*.{m,exp,inp}:
tests/declarative_debugger*/*.{m,exp,inp}:
tests/dppd*/*.m:
tests/exceptions*/*.m:
tests/general*/*.m:
tests/grade_subdirs*/*.m:
tests/hard_coded*/*.m:
Make these tests use four-space indentation, and ensure that
each module is imported on its own line. (I intend to use the latter
to figure out which subdirectories' tests can be executed in parallel.)
These changes usually move code to different lines. For the debugger tests,
specify the new line numbers in .inp files and expect them in .exp files.
Estimated hours taken: 3
Branches: main
Make the generated equality/comparison predicates for solver types that lack
user-defined equality or comparison predicates throw an exception rather than
treat the values as C pointers.
Document this in the reference manual.
doc/reference_manual.texi:
Document what happens if the user does not specify an equality or
comparison predicate in a solver type definition.
compiler/unify_proc.m:
For solver types without user-defined equality or comparison
predicates generate equality or comparison predicate that throw
an exception rather than treating the values as C pointers.
library/private_builtin.m:
Add some predicate for use by the above.
XXX type name lookups in RTTI don't seem to work properly
with solver types (or at least they have some rather
unexpected results - Mantis bug #40.)
tests/hard_coded/Mmakefile:
tests/hard_coded/solver_default_eq_cmp.{m,exp}
Test the behaviour of equality and comparison for solver
types without user-defined equality and comparison.
