I meant "nothing new to learn", it doesn't say anything but it describes them already so when you say "not in spec" I think "well, not as property", even if every engine has them, but already in specs somehow.
Hence a reason to not break de-facto legacy and think about an opt out instead Regards On Wed, Sep 17, 2014 at 5:34 PM, Allen Wirfs-Brock <[email protected]> wrote: > > On Sep 17, 2014, at 8:59 AM, Andrea Giammarchi wrote: > > FWIW that 's' flag would work for me, but about not being specd, those > properties are described already here: > > https://people.mozilla.org/~jorendorff/es6-draft.html#sec-getreplacesubstitution > > > that doesn't say anything about RegExp properties, their attributes, when > they're set, etc. It just defines how to interpret a replacement string > template. > > > and these are a long time de-facto standard. "somebody" wrote already > about them a while ago: > http://msdn.microsoft.com/en-us/library/ie/9dthzd08(v=vs.94).aspx > > > > Not spec. worthy material. Plus somebody needs to do an interoperable > semantics intersection analysis cross the major browsers. > > allen > > > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
