This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10734 - Create LR Grammar
Summary: Create LR Grammar
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-24 20:46 UTC by Kevin Lindsey
Modified: 2017-07-31 09:12 UTC (History)
5 users (show)

See Also:


Attachments

Description Kevin Lindsey 2010-09-24 20:46:33 UTC
This is a request to include an LR grammar of WebIDL in addition to the current LL grammar. Having an LR grammar would make it easier to convert for parser generators and is more conducive to building ASTs during the parse.

Thanks,
Kevin
Comment 1 Anne 2010-10-11 12:38:41 UTC
Why two ways of defining IDL fragments? That seems far worse than having just one. And it seems unlikely we will change the existing one a lot.
Comment 2 Kevin Lindsey 2010-10-11 19:21:47 UTC
Anne,

I was chatting with Cameron about this and he suggested I add a bug entry for it. Basically, an LR grammar is typically better suited for generating ASTs than LL grammars. My preference would be to have a single grammar, as well, and for that to be an LR grammar, but I'm biased.

-Kevin
Comment 3 Cameron McCormack 2011-05-23 02:55:36 UTC
Not necessary for now, so maybe in v2.
Comment 4 Arthur Barstow 2011-06-29 16:03:49 UTC
I think this bug should be Resolved now as "Later" and considered an input for v2.
Comment 5 Tobie Langel 2017-07-31 09:12:07 UTC
Maintaining two grammars is a bad idea, so we'd want to do a complete switch from one grammar to the other. There are now numerous consumers of the current LL(1) grammar, so we'd need buy-in from them before organizing such a move.

If someone's ready to do this work, I'd suggest starting a conversation on public-script-coord@w3.org before moving this to a GitHub issue, then a pull request.

In the meantime, I'll close this as wontfix.