Actually, syntax highlighting + warnings about ambiguity would be just the thing in the article's example. Suggesting that the developer choose between use of a

Actually, syntax highlighting + warnings about ambiguity would be just the thing in the article's example. Suggesting that the developer choose between use of an explicit "m" for the pattern matching: whatever m/ 25 ; # / ; die "this dies!"; ...or the use of parentheses for division: (whatever / 25) ; # / ; die "this dies!"; ...would be a helpful suggestion a syntax parser could give. Also, in either event the code is syntactically valid.