Closed GoogleCodeExporter closed 8 years ago
hm, this seems to be a bigger problem. The position calculator can handle that,
if you change the allowed characters for word borders. But the lexer will have
problems to split the tokens. There can be also some side-effects on parser
routines, which wait for empty tokens after a trim(), which will remove the
whitespace. This major problem prevents also the parsing of _utf8'haha'. I have
no simple solution for that.
Original comment by pho...@gmx.de
on 28 May 2014 at 3:49
I have added some code to the PositionCalculator, but I'm not sure, whether or
not the parser will work in all such cases. See r1363.
Original comment by pho...@gmx.de
on 28 May 2014 at 4:12
Original comment by pho...@gmx.de
on 3 Jun 2014 at 7:55
Original issue reported on code.google.com by
h.leith...@gmail.com
on 30 Apr 2014 at 9:12