I think the difference between HTML and, say, perl, is that HTML isn't so
much a programming language as the input to a program. Most programs,
especially ones for unskilled users, are in fact designed to handle
arbitrary input without crashing; html parsers are no exception.
The fact that "</table>" throws an error while "<!-- <table> --></table>"
does not suggested to me that a better algorithm might be in order. I agree
that it isn't high priority.
In the meantime, a more verbose message could help. How about something
like, "... buffer underflow (unmatched table tags while table scan is
enabled)" ?
Thanks,
Jack
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 8:25 AM
To: Gerald Richter
Cc: Jack Cushman; [EMAIL PROTECTED]
Subject: Re: </table> Stack underflow bug
Ummmmm...
Write good HTML code.
HTML has to be the only medium where users/programmers expect it not to
crash no matter what you do...
:-(
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
