🚀 go-pugleaf

In article <3330@tivoli.UUCP> taylor@foraker.tivoli.com (Eric Taylor) writes:
>>Obj. C does not have multiple inheritance.
>>I find the a BIG loss.

As a SmallTalk programmer I have found that the lack of multiple
inheritance forces me to be more complete in my analysis and seek more
complete abstractions.  Also with multiple inheritance, there is
the problem of method collision (or has that been solved ?).  In
general I think it's the easy way out.  I've bitched and moaned
when I couldn't use it - but was thankful later on that I didn't.  BTW -
there are ways to beat single inheritance.  A bit hackish but...

>>Objective C syntax is even weirder in class
>>definition than C++.

Disagree - they seem fairly simple to me.

	@interface myView:View
	{
	  id instance_variable(s)
	}
	- method_one;
	- method_two;
	- method_three;
	@end

	@implementation myView
	- method_one
	{}
	- method_two
	{}
	- method_three
	{}
	@end

>>I don't seen to remember any operator overloading
>>in Obj. C  I may be wrong.

Agree - this would be nice to have.  I'd like to redefine all the C types
and operators to make them first class classes objects and methods (like  
SmallTalk).  In an OO world EVERYTHING should be an object - right ?

Should I slip into my asbestos undees ?

--
Ronald Pomeroy
Advanced Micro Devices
CAM Applications Group
rpomeroy@aunext3.amd.com