I have a feeling that certain people are wanting to implement class-like
inheritance because it is more familiar/comfortable to them.
I strongly agree with Pascal. Prototype-based inheritance works beautifully,
and is native to javascript, so why would we want to enforce a different
type of inheritance to use the API? Most dynapi users will at least be
familiar with javascript, and may be expecting Prototype-like behavior.
It's kind of like creating a number class instead of using built in number
objects and primitive types. It's pointeless.
As far as the class/prototype argument as to what Netscape says, the first
line of this article:
http://developer.netscape.com/docs/manuals/communicator/jsobj/contents.htm
reads as follows:
"JavaScript is an object-oriented language based on prototypes, rather than,
as is common, being class-based."
-jaredn
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
