polserver/testsuite/escript/errors/errors001-two-functions-same-name.src

// reported in https://forums.polserver.com/viewtopic.php?f=54&t=6140
function foo( x )
  print( x );
endfunction

function foo( y )
  print( y );
endfunction

foo( "a" );
Update test suite for new compiler (#299) * Update test suite: - run test suite with both OG compiler and new compiler - run compiler parity test against testsuite/escript 2020-09-11 01:38:39 -07:00			`// reported in https://forums.polserver.com/viewtopic.php?f=54&t=6140`
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			`function foo( x )`
			`print( x );`
Update test suite for new compiler (#299) * Update test suite: - run test suite with both OG compiler and new compiler - run compiler parity test against testsuite/escript 2020-09-11 01:38:39 -07:00			`endfunction`

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			`function foo( y )`
			`print( y );`
Update test suite for new compiler (#299) * Update test suite: - run test suite with both OG compiler and new compiler - run compiler parity test against testsuite/escript 2020-09-11 01:38:39 -07:00			`endfunction`

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			`foo( "a" );`