polserver/testsuite/escript/func/funcref09.src

// Prints error messages for invalid number of arguments passed

print( @args0() );
print( @args1() );
print( @args2() );
print( @args2plus() );
print( @args3() );
print( "-" );
print( @args0( 1 ) );
print( @args1( 1 ) );
print( @args2( 1 ) );
print( @args2plus( 1 ) );
print( @args3( 1 ) );

function args0()
endfunction

function args1( a )
endfunction

function args2( a, b )
endfunction

function args2plus( a, b, c ... )
endfunction

function args3( a, b, c )
endfunction
Add spread operator for array initializers, function calls, and method calls (#684) * Update grammar * Update parser and AST generator * Update semantic analysis, tests * Handle instruction generation * Executor implementation - Instruction `ins_storestackcount` - Instruction `ins_spread` - Update listfile tests for new `storestackcount`` instruction * Add tests targetting resource tracker * Revert "Executor implementation" This reverts commit f0caede24179cb11b6d98c8cd1fecd91ce546148. * New instruction implementation - Introduce `BSpread` object to manage spreading an object at runtime. * More tests * Fix memory leak * Add test spreading non-arrays * Add failure reason to bfunc method call Better than getting uninit * Core changes; docs + accompanying tests for docs * Resolve CI annotation warnings - this statement may fall through * Fix listfile snapshots due to base rebase, whoops 2024-08-06 23:34:24 +02:00			`// Prints error messages for invalid number of arguments passed`

			`print( @args0() );`
			`print( @args1() );`
			`print( @args2() );`
			`print( @args2plus() );`
			`print( @args3() );`
			`print( "-" );`
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( @args0( 1 ) );`
			`print( @args1( 1 ) );`
			`print( @args2( 1 ) );`
			`print( @args2plus( 1 ) );`
			`print( @args3( 1 ) );`
Add spread operator for array initializers, function calls, and method calls (#684) * Update grammar * Update parser and AST generator * Update semantic analysis, tests * Handle instruction generation * Executor implementation - Instruction `ins_storestackcount` - Instruction `ins_spread` - Update listfile tests for new `storestackcount`` instruction * Add tests targetting resource tracker * Revert "Executor implementation" This reverts commit f0caede24179cb11b6d98c8cd1fecd91ce546148. * New instruction implementation - Introduce `BSpread` object to manage spreading an object at runtime. * More tests * Fix memory leak * Add test spreading non-arrays * Add failure reason to bfunc method call Better than getting uninit * Core changes; docs + accompanying tests for docs * Resolve CI annotation warnings - this statement may fall through * Fix listfile snapshots due to base rebase, whoops 2024-08-06 23:34:24 +02:00
			`function args0()`
			`endfunction`

			`function args1( a )`
			`endfunction`

			`function args2( a, b )`
			`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 args2plus( a, b, c ... )`
Add spread operator for array initializers, function calls, and method calls (#684) * Update grammar * Update parser and AST generator * Update semantic analysis, tests * Handle instruction generation * Executor implementation - Instruction `ins_storestackcount` - Instruction `ins_spread` - Update listfile tests for new `storestackcount`` instruction * Add tests targetting resource tracker * Revert "Executor implementation" This reverts commit f0caede24179cb11b6d98c8cd1fecd91ce546148. * New instruction implementation - Introduce `BSpread` object to manage spreading an object at runtime. * More tests * Fix memory leak * Add test spreading non-arrays * Add failure reason to bfunc method call Better than getting uninit * Core changes; docs + accompanying tests for docs * Resolve CI annotation warnings - this statement may fall through * Fix listfile snapshots due to base rebase, whoops 2024-08-06 23:34:24 +02:00			`endfunction`

			`function args3( a, b, c )`
			`endfunction`