Parser interprets expressions in commands wrong

[Fabian Maurer]

say toString(1);

bad argument #0 (string expected, got function)

say ""..toString(1);

bad argument #1 (string expected, got number)

[Chimaine]

is this actually for 2.0 or 2.1? Because it's filled as for 2.0 :)

[Fabian Maurer]

Uhm, should be 2.1, I used "MobTalker2-1.6.4-0.3.1-alpha".

[Chimaine]

Seems to be a specific issue with commands. The parser derps and decides that toString is actual a variable access and (1) is an expression in parentheses.

As a temporary workaround, wrap the call in parentheses to force the parser to interpret it correctly.

say ( toString( 1 ) );
say "" .. ( toString( 1 ) );

[Chimaine]

Removing version: 2.1 (automated comment)

[Chimaine]

This issue has been ongoing for a while now. Setting this to critical so it gets fixed before the next minor version bump.

[Chimaine]

Wait, setting the version is wrong, that should be Milestone...

[Fabian Maurer]

Seems to be still persistant in MT0.5.0, same error with the inital code samples.

[Chimaine]

Hopefully fix #10 for good.

→ <<cset b9c617771ce0>>

[Fabian Maurer]

Still persistent, with the same errors with the initial code samples.

[Chimaine]

sigh

[Chimaine]

Solving this will require a syntax change. Combine this with #26