« Bugzilla Issues Index

#1414 —, undefined [[StringData]] case not handled

With the latest changes it's possible for [[StringData]] to be undefined. [[HasOwnProperty]] and [[GetOwnProperty]] for String Exotic Objects needs to be updated to handle this case.

fixed in rev 15 editor's draft.

Setting [[StringData]] to undefined is intended to just be a spec level flag to tag instances that have not yet been constructor initialized. I don't really want to add an extra check for that in the internal methods. Instead, I specified for them that undefined [[StringValue]] is treated as if its value was an empty string.

It's really up to implementation to decide how to identify uninitiated instances and get their constructor initialization logic to work as specified.

resolved in rev 15, May 14, 2013 draft