You're right: the constructor property doesn't work property even in an
unoptimized beget() function. I retract my previous message. I sent it
without testing my assertion. That was careless, and I apologize.
My carelessness, however, is not sufficient reason for you to accuse me
of posting without reading or thinking. This is a -dev level mailing
list. You must assume that all posters here are well-read and
thoughtful. Otherwise you sound paternalistic!
David Flanagan
Andrea Giammarchi wrote:
> David, read carefully, think, and try again ....
>
> On Tue, Aug 11, 2009 at 11:16 PM, David Flanagan
> <da...@davidflanagan.com <mailto:da...@davidflanagan.com>> wrote:
>
>
> Of course, if you optimize it in this way to share a single constructor
> function, you can't find the prototype of an object created with beget()
> with o.constructor.prototype. Not sure how important that is, but there
> is a downside to the optimization.
>
> David
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
