Fixed typo in line 47

[gregvinyard]

The original statement, "x=0 :out=ifa" makes no sense as the :out assignment makes no reference to x.

[martindevans]

Did you double check this result in game to make sure it still produces the expected value?

[gregvinyard]

I did not, originally. It just didn't make sense to assign 0 to x, and then not use x. I did just do some testing, and the whole line seems fishy now. You can put anything after the "if" and :out will still equal 0.

x=0 :out=ifa -> 0
x=0 :out=ifx -> 0
x=0 :out=if1 -> 0
x=0 :out=if(1) -> 0
x=1 :out=ifx -> 0

I think the issue is "if" doesn't return anything that can be assigned to the variable :out.

[dbaumgarten]

I think originally this line was intended to test yolol's weird Contest-sensitive parsing.
Code sometimes parses differently depending on if some variable has been previously used or not.
(These lines had been tested one by one, so during testing that line "a" was not assigned).

Also: The whole line IS fishy. Any variable containing a keyword will break things. "ifa" contains "if" and therefore causes a parser-error.

[gregvinyard]

In that case, the line seems like it's testing two things. One, whether using the keyword "if" will cause a parsing error and two, if using an undeclared variable will cause an error.

If that's the case then it makes more sense to have two lines so you're only doing one test at a time:
x=0 :out=a -> 0
x=0 :out=ifx -> 0

Either that or I am missing something, which is completely possible. 😅

[dbaumgarten]

Yes, splitting it in different tests would probably be good.
Additionally the test-case with "ifx" should have a check to verify that the remaining part of the line is actually skipped.