I’m still trying to find a practical use for IE’s implementation of toString on COM’s…

valueOf, hasOwnProperty, et c. Not avaliable.

Interestingly, toString is available.

What is even more interesting: acts like a “DontEnum” property, so for(prop in node) , “toString” won’t be exposed.

IE doesn’t actually implement the internal “DontEnum” property correctly (at least in my interpretation of the ECMAScript Spec.

so

Carp = {
“toString” : function(){ return “Carp, carp, carp”; }
}

for(var prop in Carp)
alert(Carp[prop]);
}

IE thinks that the “toString” defined in Carp has a DontEnum property on it, and this is what I think is incorrect. I think IE is iterating through a list of strings (”toString”, “valueOf”) and skips any prop that matches the string.

I’ll change the example.

This may be irelivant here, but if I recall correctly… the structure of appendChild is:

appendChild( arg_0 );

(e.g. arity == 1)

That, coupled with the fact that appendChild is a “method” on a DOM node, this scenario is a bit whacky.

Finally, you can’t add a text node, to {document}… if you wanted to, you could add it to say… document.getElementsByTagName(’body’)[0]

E.g.

document.getElementsByTagName(’body’)[0].appendChild(document.createTextNode(’Huh?’));

Now, that all said, the following code, as you mentioned, still doesn’t work.

var f = document.getElementsByTagName(’body’)[0].appendChild;
alert(f); //Native Function…
alert(f.arity); //1 (only 1 argument expected)…
f.call( document.createTextNode(’Huh?’) );

Cheers,
Steve