> > I've tried implementing python style slice on both strings and arrays in
the past (I don't seem to have an existing branch with it in any more > though it seems). The biggest problems I hit were regarding the syntax, the > functionality itself worked. If you've got a link to your messaging thread, I'd love to read it. Thanks Colons caused problems with ternary operators in the lexer, and I had an > issue with commas too, but I forget what it was. Of course these might have > been resolvable, but I didn't put too much effort into it. Could this not be mitigated by adding a new token like T_COLON to be used to match this use case?
