block scope + direct non-strict eval

Allen Wirfs-Brock allen at wirfs-brock.com
Thu Feb 2 09:06:53 PST 2012


Also, please report all draft spec. issues using bugs.ecmascript.org.  That way they won't get lost in the noise on this list.  You can also submit issues against proposals using it.

Allen

On Feb 2, 2012, at 8:33 AM, Allen Wirfs-Brock wrote:

> In general, my job as editor is to turn proposal into to actual normative specification language. Informally at any point in time, a wiki proposal is in one of three states relative to the draft ES6 specification.  The states "in the draft spec",. "not yet in the draft spec", or "draft spec. work in process". 
> 
> For proposal that are "in the draft spec", the spec should be the primary think you look at as it reflects my understanding of all current decisions and is the normative text that ultimately needs to be correct. Sometimes there are open issues that are explicitly noted in the draft.  I generally "immediately" (within a week or so) after a TC39 meeting update the draft spec. to reflect any decisions that were made concerning "in the draft spec features".  Once something is "in draft spec", the wiki pages become many useful as background material. 
> 
> I find that for most proposal there are many details that need to be specified that were not covered by the proposal.  I generally bring to this list any such details that have a significant impact, are likely to be controversial,  or for which that are multiple plausable alternatives.  But  for the rest I simply resolve them in a manner that I believe is most consistent with the overall language.  This is why it is important that people review the actual specification language. In the end, its the only thing that counts.
> 
> For  proposal that are "not yet in the draft spec", it would certainly be helpful if the champions of such proposal kept them up to date.
> 
> I treat proposals that are  "in process for the draft", similarly to "in the draft spec" items.  But it would be helpful for the champions to also update the proposal pages.
> 
> Bottom line, always start with the draft spec.  Then refer to proposals.
> 
> Allen
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20120202/28daa0ac/attachment.html>


More information about the es-discuss mailing list