P
Peter Michaux
Hi,
I am reading the ECMAScript specs trying to figure out if the next
line is a legal statement or not
new Foo();
I think the above code may only be legal as an expression and not as a
stand alone statement. Would this make the above a bug?
Douglas Crockford's JSLint will choke on the above line of code and
stop parsing. All the browsers seem to accept it as ok and work as I
expect: the returned object just doesn't get assigned to anything.
The time I have used a line like the above is when the constructor has
side effects and the "class" keeps track of all its instances.
Any ideas what is right or wrong in this case?
Thanks,
Peter
I am reading the ECMAScript specs trying to figure out if the next
line is a legal statement or not
new Foo();
I think the above code may only be legal as an expression and not as a
stand alone statement. Would this make the above a bug?
Douglas Crockford's JSLint will choke on the above line of code and
stop parsing. All the browsers seem to accept it as ok and work as I
expect: the returned object just doesn't get assigned to anything.
The time I have used a line like the above is when the constructor has
side effects and the "class" keeps track of all its instances.
Any ideas what is right or wrong in this case?
Thanks,
Peter