On May 26, 2011, at 1:09 PM, Michael Haufe wrote:
> Is there any plan to standardize Sharp Variables or something similar?
>
> https://developer.mozilla.org/en/Sharp_variables_in_JavaScript
No plans. I tried in 1998 or 1999, when TC39 was doing ES3. Rok Yu, then of
Microsoft, argued against standardizing serialization since it was
domain-specific and best done by libraries (unfortunately until WeakMaps in
ES.next, implemented in Firefox nightlies, there has not been an efficient way
to handle the join-points and cycles that sharps handle). Also, some hated the
syntax.
The plan of record at Mozilla is recorded here:
https://bugzilla.mozilla.org/show_bug.cgi?id=486643 (deprecate sharp variables)
https://bugzilla.mozilla.org/show_bug.cgi?id=566700 (remove sharp variables)
The bugs must be fixed in that order, with a release in between.
The deprecation bug has an attachment,
https://bugzilla.mozilla.org/attachment.cgi?id=513490
written by Jason Orendorff, that is a self-hosted implementation of
{Array,Object}.prototype.toSource. The idea is to self-host all of uneval, and
provide a sharp-parsing version of eval or JSON.parse if needed. At the end of
the deprecation/removal cycle, sharps would be implemented by "library code"
only. No hardcoded syntax.
/be_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss