- From: Ian Hickson <ian@hixie.ch>
- Date: Sat, 23 Oct 2004 17:58:30 +0000 (UTC)
- To: David Woolley <david@djwhome.demon.co.uk>
- Cc: www-style@w3.org
On Sat, 23 Oct 2004, David Woolley wrote: >> >> That's mostly because the grammar in the CSS2.1 draft doesn't really >> handle the error correction for unexpected EOF cases. A comment really >> should be defined as starting with "/*" and ending with "*/" _or_ the EOF. >> Similarly for other things like blocks, matched parentheses, etc. > > Which in turn is because the grammar requires properly nested and > closed structures, but the obvious intention is that rules be actioned as > soon as they have been completely read. Right -- it's definitely intended for CSS to be parsable with no more than one character look-ahead, so anything that implies otherwise is most probably incorrect. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 23 October 2004 17:58:32 UTC