Open GoogleCodeExporter opened 8 years ago
This is a real issue and a good example of why swinging regexp parsing is
always subpar to real parsing.
Not sure how can we detect this at all.
Original comment by t.br...@gmail.com
on 3 Oct 2010 at 5:58
A hacky solution might be to look at the char before the regexp (though it just
hit me that it might not have access to that when pattern-matching).
The char following might not be useful, you could very well divide something
with a var named g.
Original comment by petterson.erik@gmail.com
on 7 Oct 2010 at 6:52
Original issue reported on code.google.com by
mlunar
on 3 Oct 2010 at 12:39Attachments: