This is good - I think JS users right now want to be assured that all of the code they're writing will continue to work as we move forward with the language.
khs On Fri, Feb 17, 2012 at 8:47 PM, David Herman <[email protected]> wrote: > On Feb 17, 2012, at 3:36 PM, Isaac Schlueter wrote: > > > Brandon, > > > > That's a bug in v8. The "module" identifier is only supposed to be > > reserved in a very specific context. The required context is not > > valid syntax today, so it's safe to say that no one's using it yet. > > > > Bugs in v8 are rare enough that this really confused me as well. I > > thought for sure something had slipped into the spec. Here's the > > report: http://code.google.com/p/v8/issues/detail?id=1957 > > To be fair, it was only very recent that we started talking about not > reserving 'module' as a keyword, so v8 was just implementing what seemed > like where ES6 was going at the time. > > Dave > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
