Author birknilson
Recipients Arfrever, birknilson, ezio.melotti, zmedico
Date 2013-02-23.20:54:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361652852.99.0.698292427745.issue16121@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-02-23 20:54:13birknilsonsetrecipients: + birknilson, ezio.melotti, Arfrever, zmedico
2013-02-23 20:54:12birknilsonsetmessageid: <1361652852.99.0.698292427745.issue16121@psf.upfronthosting.co.za>
2013-02-23 20:54:12birknilsonlinkissue16121 messages
2013-02-23 20:54:12birknilsoncreate