polserver/testsuite/escript/test/test6.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

9 lines
435 B
Text

print( "this is a test script." );
print( "This is really more correct," );
print( "But the parser is currently somewhat" );
print( "flexible." );
print( "This kind of " + ( "Thing" + " " + "is" ) + " trouble, though," );
print( "because after the parser sees a left paren, it exits on the" );
print( "next one (if it is parsing a function)." );
print( "This " + "is " + ( "the correct fucking way" - " fucking" ) + " to do this." );