Message182820
The implementation incremented the line number immediately when a newline was detected, even before the token had been processed completely - causing the issue Arfrever posted.
This also caused the unexpected behavior of a tokens line number including the amount of lines within the token itself. In other words '"a \n b \n c" \n d' would result in the token "a \n b \n c" to have the line number #3, followed by "d" being on the expected line #4. In my patch, the expected behavior of seeing the first token on line #1 and the second on #4 is introduced.
I also added the testLineNumbers method in the test suite - included in the patch. |
|
Date |
User |
Action |
Args |
2013-02-23 20:54:13 | birknilson | set | recipients:
+ birknilson, ezio.melotti, Arfrever, zmedico |
2013-02-23 20:54:12 | birknilson | set | messageid: <1361652852.99.0.698292427745.issue16121@psf.upfronthosting.co.za> |
2013-02-23 20:54:12 | birknilson | link | issue16121 messages |
2013-02-23 20:54:12 | birknilson | create | |
|