On 1 Jan 2008, at 15:39, Andy Armstrong wrote:
Is there a compelling reason not to remove switch, case and move
select to the functions list?
The switch/case might be the result of initially basing the grammar on
the C grammar. So presumably it should be removed.
Also, because I'm a TM language definition newbie,
does anyone have
any tips about how to handle the // (defined or) operator? In some
contexts // is an empty regex; in others it's an operator
In the Ruby grammar we have a list of functions that take regexp
arguments to solve the division/regexp ambiguity -- something similar
could be done for perl wrt the split case.