To be honest, I was championing that parser writers should write flexible and supportive parsers and put strict ocd parsing under a flag/option. Especially in this case, where you need a parser that should be able to parse content parsable by a number of other parsers (-> browsers), you want your parser to be as accepting as possible or it's useless in those contexts.
I'm not saying "bring back `f()=x`" :) I don't see any point in that myself. Thanks though, David. - peter On Wed, Aug 7, 2013 at 1:08 PM, David Bruant <[email protected]> wrote: > Hi, > > From http://qfox.nl/weblog/291 > Apparently, "f() = x" was forbidden as of ES5.1 (was still available in > ES5 apparently), but a jQuery plugin is using it [1] (path not triggered in > non-IE browsers). > Not breaking the web, all that. It should probably be brought back. > > Syntax isn't my cup of tea, so I'll let others judge if a detail was > overlooked somewhere. > > Kudos to @kuvos on this one! > > David > > [1] http://www.thuisbezorgd.nl/**scripts/jquery/jquery.** > placeholder-min.js<http://www.thuisbezorgd.nl/scripts/jquery/jquery.placeholder-min.js> > ______________________________**_________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss> >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
