|
![](/i/fill.gif) |
It is so easy to change a parser to check for this condition
that the fact it is a common problem doesn't make it not a problem,
however.
There are valid reasons that one might want to omit a newline
from a file end. But I can think of no reason a parser
would not want to conclude EOF was a line terminator (unless
this is viewed as some sort of scheme to catch truncated
files)
So I agree with "ingo" that this is validly called a bug.
Dan
P.S. Thanks for the LINUX port, but that's for another group...
Ron Parker wrote:
> This is a common problem for a lot of languages. So much so, in fact, that
> people in at least one other newsgroup will tell you that if your editor
> allows you to create a text file with no newline after the last line, then
> the flaw lies in your editor, not in the parser. I tend to agree with them.
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
![](/i/fill.gif) |