- From: <bugzilla@jessica.w3.org>
- Date: Fri, 04 Mar 2011 07:10:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11977 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-03-04 07:10:02 UTC --- Will fix the issues you raise, thanks. > > It would be really nice if the JS spec could just give us hooks that we could > > use so that we didn't have to worry about updating HTML every time the JS spec > > revs. > > I agree with the goal, but there are some missing ES semantics we still need to > address. In this particular case, I think we may be able to describe the > desired semantics as a source-to-source transformation of the ES code and avoid > having to explicitly reach into the ES5 internal spec. mechanisms. I really would like to avoid defining a source transformation because that often ends up having far more complicated side-effects than one would expect. What I mean by a "hook" is just that the ES spec could say "When a specification needs to create a foo using a list of arguments bar and a body baz, it must follow these steps, which return a quux and a gizmo: 1. do something, 2. do something else, 3. do yet more things". Then instead of having to reference specific sections or talk about specific grammar constructs, we can just say "and then create a foo as defined in the ES spec". There's a number of places where hooks like that would be useful. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 4 March 2011 07:10:08 UTC