mirror of
https://github.com/polserver/polserver
synced 2026-08-13 08:23:08 -04:00
3ccf701ce9
* 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
16 lines
507 B
Text
16 lines
507 B
Text
use math;
|
|
|
|
// This isn't supposed to compile, but it does. It works because the emitted
|
|
// code to call a module function (with 0 parameters) is a single instruction.
|
|
//
|
|
// This is more commonly seen in NPC control scripts, which often do
|
|
// something like this:
|
|
// const me := self();
|
|
//
|
|
// The intent is likely brevity and efficiency, but this will result in
|
|
// repeated calls to the module function, rather than storage and reuse
|
|
// of the result of a single call.
|
|
|
|
const PI := ConstPI();
|
|
|
|
print( PI );
|