3 Commits

Author SHA1 Message Date
Zoltan Somogyi
d23c4f74a3 Update the style of more tests. 2020-10-06 19:20:18 +11:00
Zoltan Somogyi
33eb3028f5 Clean up the tests in half the test directories.
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.
2015-02-14 20:14:03 +11:00
Julien Fischer
26941b5a06 Overflow in string-to-float conversions.
The behaviour of string.to_float/2 is not currently consistent between backends
when the conversion overflows.  The C and Java backends return infinity or
-infinity, while the C# backend fails.  Fix this by specifying that
string.to_float/2 should return infinity or -infinity on the conversion
overflowing and modify the C# implementation to do this.

library/string.m:
	Specify what happens when string.to_float/2 overflows.

	Address the XXX in the C# implementation of string.to_float/2:
	we need to catch System.OverflowException.  If we do catch
	it then return +/- infinity as appropriate.

	Fix a typo: s/Formating/Formatting/

tests/hard_coded/Mmakefile:
tests/hard_coded/string_to_float_overflow.{m,exp}:
	Add a test for string-to-float conversion overflow.
2014-12-22 13:06:12 +11:00