On Sun, 13 Sep 2009 01:39:43 +0400, kangax kan...@gmail.com wrote:
On Sep 12, 3:05 am, artemy tregubenko m...@arty.name wrote:
This may used to unobtrusively store in a hash some data associated
with dom nodes.
So DOM node would be a key? That doesn't really sound like a good
idea. The
Sometimes the most productive results come from the most dangerous of
tools.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
var h = $H({});
h.set('__proto__','sadfdsf');
alert( typeof( h.get('__proto__') ));
Also try these:
alert(Object.toQueryString('hasOwnProperty=1'.toQueryParams()));
// hasOwnProperty=function%20()%20%7B%20%5Bnative%20code%5D
%20%7DhasOwnProperty=1
May be
++IE dontEnum bug =)
var h = $H({});
h.set('toString',1);
alert(h.toJSON());
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to
On Sep 13, 9:32 am, Yaffle vic99...@yandex.ru wrote:
var h = $H({});
h.set('__proto__','sadfdsf');
alert( typeof( h.get('__proto__') ));
That's a known limitation, actually (although, probably not documented
anywhere). There's no key coercion in Prototype's Hash implementation,
which is why
I've just gotten a chance to look at the new PDoc-generated
documentation, and I think making a few stylistic changes would really
improve the usability of the new docs:
* Class methods no longer immediately listed under class header, and
are difficult to distinguish while skimming. A simple fix
You're right, `hasOwnProperty` can be useless, and
`propertyIsEnumerable` is useless becauseof dontEnum IE bug...
Why not to patch Hash to use some prefix for keys?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Why not to patch Hash to use some prefix for keys?
That was my plan for 1.7, actually.
It fixes that issue and also avoids creating an extra, internal
object.
Good to see that we're on the same page, here.
Tobie
--~--~-~--~~~---~--~~
You received this message
On Sep 13, 6:38 pm, Tobie Langel tobie.lan...@gmail.com wrote:
Why not to patch Hash to use some prefix for keys?
That was my plan for 1.7, actually.
It fixes that issue and also avoids creating an extra, internal
object.
Sorry, I'm not following. How does prefixing a key avoid object
