[whatwg] 126.96.36.199: EOF handling
Edward Z. Yang
edwardzyang at thewritingpot.com
Mon Dec 22 13:46:07 PST 2008
Philip Taylor wrote:
> EOF is always treated as if it were a character, e.g. lots of places
> say "Consume the next input character: ... EOF -> ... Reconsume the
> EOF character in the data state".
That seems fair, although most implementations won't have an actual end
of file character; they'll be checking their string index to see if
they've gone out of bounds. But the spec is internally consistent (I'm
just used to seeing an EOF special case on almost every state).
More information about the whatwg