Thanks very much, and I think this constructor property is really not
very reliable, such as:
function a(){}
a.prototype={b:123}
b=new a
b.constructor==Object //true
and:
function a(){}
a.prototype=new String("aaa");
b=new a;
b.constructor==String
you can change the constructor before or after you
> So Tobie, how would you use the file protocol for an ajax request?
It's mainly a backwards compatibility issue (plus it can be useful for
testing purposes).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Protot
When you create a new function it has a "prototype" property, which
has a "constructor" property which refer to the created function:
function F(){};
F.prototype.constructor === F => true
So you will be able to get the class of an instance:
var obj = new F;
obj.constructor === F => true
Whe
FYI, Custom Search has been around for about a year.
http://www.google.com/coop/cse?cx=000270142967387495712%3A7a7oj26tkbm
Just because its on digg doesn't make it new.
Certainly, props for the good intention.
On Sep 7, 5:15 pm, kangax <[EMAIL PROTECTED]> wrote:
> Ok, guys.
>
> As you all might
I have seen the new inheritance code from Alex in 1.60 rc0, and I have
a question: I believe the following two lines code are no use at all
method.prototype.constructor = method;
subclass.prototype.constructor = subclass;
constructor property is no use at all, the usage property is __proto
