polserver/testsuite/escript/bracket/bracket.src
Kevin Eady 3ccf701ce9
Format testsuite scripts, pol-core support modules (#713)
* Format escript testsuite

* Manual formatting for escript testsuite
- Add format-off to places where formatter does what it should, but we don't like the results
- Manually change places where formatter outputs weird things _without_ format-off, so next format-all would show changes if not fixed

* Update .err files; add update_err.py helper script

Use the format `:line:col: message` for all .err file checks. This
allows us to change the file names without needing to edit the .err
contents.

Note that `in/inc0{1,2}.err` need have error messages between POSIX and
Windows, so their messages are a bit more "generic" than the other errs.

* Format pol testsuite

* Manual formatting for pol testsuite

* Format pol-core modules

* Manual formatting for pol-core modules

* Additional format pol-core modules

Use FormatterLineWidth=10000 since module functions must be on one line
because of the parse_modules target

* Address Discord comments

- Support multi-line module function declarations in parse_modules

* Format on df07831
2024-10-04 10:29:55 +02:00

56 lines
824 B
Text

print( "Testing Simple IF:" );
if ( 5 < 3 )
print( "1a: failure 1" );
endif
if ( 3 < 5 )
print( "1b: ok" );
endif
print( "Testing IF..ELSEIF..ENDIF" );
if ( 3 < 5 )
print( "2: ok" );
elseif ( 3 < 5 )
print( "2: failure 1" );
endif
print( "Testing IF..ELSE..ENDIF" );
if ( 3 < 5 )
print( "3a: ok" );
else
print( "3a: failure 1" );
endif
if ( 5 < 3 )
print( "3b: failed" );
else
print( "3b: ok" );
endif
print( "Testing IF..ELSEIF..ELSE..ENDIF" );
if ( 3 < 5 )
print( "4a: ok" );
elseif ( 4 < 6 )
print( "4a: failure 1" );
else
print( "4a: failure 2" );
endif
if ( 7 < 5 )
print( "4b: faiure 1" );
elseif ( 4 < 6 )
print( "4b: ok" );
else
print( "4b: failure 2" );
endif
if ( 7 < 5 )
print( "4c: faiure 1" );
elseif ( 9 < 6 )
print( "4c: failure 2" );
else
print( "4c: ok" );
endif