polserver/testsuite/escript/string/string19.src

// 2015-19-12 Bodom, testing escape sequences

print( "testing\nescapes:\t\\\x48\x65\x6c\x6Co\x21" );
Unit tests: adding escript tests for new \xFF escape sequence 2015-12-19 03:09:09 +01:00			`// 2015-19-12 Bodom, testing escape sequences`

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			`print( "testing\nescapes:\t\\\x48\x65\x6c\x6Co\x21" );`