You have to agree that the use of a phrase like "abstract class",
even if technically not incorrect in the context of Objective-C,
risks leading folks new to Objective-C and Cocoa, especially those
with some C++ background, astray.
Bob, I suggest that you file an enhancement request against the
docs...
I do agree, and I posted the following feedback using the link at the
bottom of the NSView doc page:
- - -
The use of the term "abstract class" in the "Class at a Glance"
section can easily confuse people coming from other languages where
the term has a specific meaning. Having used Smalltalk, C++, and
Java, I think of an abstract class that can't or shouldn't be
instantiated. But it's not only possible but perfectly fine to
instantiate NSView, as proven by CustomViews and tab views in IB.
The problem is compounded by the fact that, as far as I can tell, the
term "abstract class" is not explained anywhere for the Objective-C/
Cocoa context.
Is it possible that the Objective-C documentation for NSView was
copied from the Java documentation? Is the Java version of NSView in
fact abstract? But then how would Cocoa-Java have been able to read
nib files?
- - -
--Andy
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
