Hi, Is has been reported that the grammar for the body of @page rules (that allows mixed declarations and at-rules) is not LL(k). In other words, it requires unbounded look-ahead. https://www.w3.org/Style/CSS/Tracker/issues/263 css3-syntax defines the same syntax for all declarations blocks. The state machine there is clearly unambiguous and only requires bounded look-ahead. But the only ways I found to translate this state machine into the traditional grammar operators (concatenation, alternation, repetition, etc.) required unbouded look-ahead to pick between the branches of a declaration that ends with ';' or one that ends with '}'. Should we care about this? Is it a problem for grammar-based parser implementations? -- Simon SapinReceived on Saturday, 2 February 2013 19:01:46 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:26 UTC