8.2.4 The Reference Specification Type

John J Barton johnjbarton at johnjbarton.com
Tue Dec 18 12:08:03 PST 2012

On Tue, Dec 18, 2012 at 11:39 AM, Allen Wirfs-Brock
<allen at wirfs-brock.com>wrote:

> ...
> I'r all in and (GetValue/SetValue).
> Consider  an expression like:
>     123.0.toFixed
> This evaluates to a Reference value {base: 0, referenced name: "toFixed",
> strict: false}
> (or strict is true if in strict code)
> GetValue/SetValue explicitly coerces primitive base values to Objects in
> order to do property lookup.
> In general, within the ES6 spec, the introduction of symbols as property
> keys introduces some confusion about the implications of the work "name".
>  I'm slowly migrating some uses of "name" to "key".  However, symbols
> doesn't seem to be the source of your problem here.

No, indeed. The source of my problem was to much C-heritage: I could not
imagine 123.0.toFixed(). (Plus that could not be the explanation since I've
not been able to understand any of the discussion about the mysterious
'symbols' ;-)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20121218/174e2333/attachment.html>

More information about the es-discuss mailing list