I wonder which part of JS prototypal inheritance is not part of JS. new
keyword exists since ages so what is the problem about "new", inheritance,
and constructors?
On the other hand I must agree that jQuery is all but inheritance!
If we need our prototypal based application why should we bother jQuery
which aim is to manipulate DOM and/or associated events?
It is like: I can't get by without Element.prototype.createBedge ... would
you put such method for each DOM Element?
I don't think so, and we have cloneNode or just jQuery(stuff).clone(), which
makes sense.
function A(){};
function B(){};
(B.prototype = new A).constructor = B;
it is just that simple, and it has nothing to do with jQuery, imho.
On Thu, Aug 13, 2009 at 11:52 AM, DBJDBJ <dbj...@gmail.com> wrote:
>
> I do agree with 'tres' that we (in essence) should not try to change
> JS into something which it is not
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
