W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2017

[Bug 28065] WebIDL: Grammar for readonly requires 2 token lookahead in some cases

From: <bugzilla@jessica.w3.org>
Date: Mon, 31 Jul 2017 14:27:47 +0000
To: public-script-coord@w3.org
Message-ID: <bug-28065-3890-Cn8CHv4Z3K@http.www.w3.org/Bugs/Public/>

Tobie Langel <tobie.langel@gmail.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Tobie Langel <tobie.langel@gmail.com> ---
(In reply to Boris Zbarsky from comment #2)
> Because now ReadOnlyMember and ReadWriteAttribute are separate things under
> InterfaceMember?

Yes? I still find it super hard to reason about this tbh.

> I _think_ so.  It's a bit weird that ReadWriteAttribute includes "inherit
> ReadOnly AttributeRest" (as in, "ReadWriteAttribute" is a bad name for that
> production), but I _think_ there's no grammar problem.

Agree the name is bad. I should probably do a cleanup of the grammar at some
point, but I don't think it's a top priority right not.

> I won't know for
> sure unless/until we try to update our grammar to match the one in the spec
> right now and see whether the tools complain...

Sounds good. I'll close this as invalid (not sure what the keyword is for "no
longer an issue"). And we can file a new issue if this turns out to be a
problem again.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 31 July 2017 14:27:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:25 UTC