polserver/testsuite/escript/string/string17.src

var a := "testvalue";

if ( a[3] < a[4] )
  print( "1: Success" );
else
  print( "1: Failure!" );
endif

if ( a[2] > a[1] )
  print( "2: Failure" );
else
  print( "2: Success" );
endif
found a testsuite in the cvs, last change was somewhere in 2003... damn it updated the scripttests to current escript we need more tests!!! and we need to pimp the whole teststructure :) HowTo: compile runecl, ecompile compile bcomp change to vs cmdprompt and go to escript dir "nmake" runs the tests "nmake clean" - cleans them ... to run the test with x64 modify the makefile 2011-12-29 21:42:26 +00:00			`var a := "testvalue";`

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			`if ( a[3] < a[4] )`
			`print( "1: Success" );`
found a testsuite in the cvs, last change was somewhere in 2003... damn it updated the scripttests to current escript we need more tests!!! and we need to pimp the whole teststructure :) HowTo: compile runecl, ecompile compile bcomp change to vs cmdprompt and go to escript dir "nmake" runs the tests "nmake clean" - cleans them ... to run the test with x64 modify the makefile 2011-12-29 21:42:26 +00:00			`else`
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( "1: Failure!" );`
found a testsuite in the cvs, last change was somewhere in 2003... damn it updated the scripttests to current escript we need more tests!!! and we need to pimp the whole teststructure :) HowTo: compile runecl, ecompile compile bcomp change to vs cmdprompt and go to escript dir "nmake" runs the tests "nmake clean" - cleans them ... to run the test with x64 modify the makefile 2011-12-29 21:42:26 +00:00			`endif`

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			`if ( a[2] > a[1] )`
			`print( "2: Failure" );`
found a testsuite in the cvs, last change was somewhere in 2003... damn it updated the scripttests to current escript we need more tests!!! and we need to pimp the whole teststructure :) HowTo: compile runecl, ecompile compile bcomp change to vs cmdprompt and go to escript dir "nmake" runs the tests "nmake clean" - cleans them ... to run the test with x64 modify the makefile 2011-12-29 21:42:26 +00:00			`else`
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( "2: Success" );`
found a testsuite in the cvs, last change was somewhere in 2003... damn it updated the scripttests to current escript we need more tests!!! and we need to pimp the whole teststructure :) HowTo: compile runecl, ecompile compile bcomp change to vs cmdprompt and go to escript dir "nmake" runs the tests "nmake clean" - cleans them ... to run the test with x64 modify the makefile 2011-12-29 21:42:26 +00:00			`endif`