CONST does not produce an error on invalid syntax such as two digits in a row

[mkilgore]

This is fairly simple, the line CONST foobar = 2 3 4 5 should be invalid syntax, but instead it is treated as though you wrote CONST foobar = 2345. This is due to some logic in PreParse, which is part of the Evaluate_Expression$ logic. Early on in PreParse all spaces are removed from the expression and for invalid expressions such as this example that ends up producing valid syntax and thus no error is produced.

[mkilgore]

I'm not entirely sure how related this is to my above example, but CONST foobar = OR 2 is also incorrectly treated as valid. It seems any boolean expression can be used in this fashion and it seemingly treats the first argument as zero (but that may not stay the case in more complex scenarios).