20 Sep
2003
20 Sep
'03
6:17 a.m.
Ideally we'd like to keep everyone happy. Sometimes that's not possible, and this is one of those cases. Now, the 'with' keyword isn't doing anyone any harm where it is apart from adding a bit of complexity to the parser, and I'm not really bothered by that, so I really don't mind leaving it in if you're still using it.
Except that it conflicts with an identifier used in a standard library. Could we fix this using the same ugly hack we use for the 'as' keyword? That is, treat it as a keyword only when used in the right context. I'm not sure of the answer - seems like it would require extra lookahead to decide which way 'with' is being used. -- A