🚀 go-pugleaf

In article <1iv5ijINN8ba@pith.uoregon.edu> bjorn@darmok.uoregon.edu (Bjorn S.  
Fjeld Pettersen) writes:
> In article <1993Jan12.165154.26915@dvorak.amd.com> rpomeroy@aunext1.amd.com  
> (Ron Pomeroy x(Coop)) writes:
> > In article <63320@mimsy.umd.edu> alex@cs.umd.edu (Alex Blakemore) writes:
> > >>I thought some Obj-C users would find it interesting.
> > [munch munch]
> > >>
> > >>                       ANNOUNCEMENT OF A LECTURE
> > >>                       
> > >>                    
> > >>                    -- "THE DARKER SIDE OF C++" --
> > >>                    
> > >>                     Wednesday, January 27, 1993
> > >>               15.15 o'clock (end at 17.00 at the latest)
> > >>
> > >>
> > >>          Ecole Polytechnique Federale de Lausanne - Site Ecublens
> > >>          Batiments du Departement d'informatique - room INR 219
> > >>         
> > >>
> > >>           by MARKKU SAKKINEN, University of Jyvaskyla, Finland
> > >>
> > >>
> > [munch munch]
> > 
> > >>The worst disadvantage of C++ at the moment is political:  accepting
> > >>C++ as the standard OO language de facto tends to kill other existing
> > >>languages, and stifle the development of a new generation of
> > >>essentially better OO languages.
> > 
> > Aaaaaaaaaamen!!
> > 
> > --
> > Ronald Pomeroy		[Objective-Cruntime: [Smalltalk runtime]];
> 
> When I can do this in Obj-C I would be happy (tm):
> 
> 	String a = "hello", b = " ", c = "world";
> 	cout << a + b + c + '\n';
> 
> Until then things (tm) look soooo much prettier in C++.
> (BTW, where is that multiple inheritance in Obj-C???)
> 

Where are those productivity gains in C++?  Where is that real run-time  
binding in C++?  Where are those Distributed Objects seamlessly integrated  
into the language?  Sorry, but you won't see that on C++?

Operator overloading **is cool and simplifies notation**.  It's pretty handy  
for complex numbers and strings.  But it does NOT have as much impact on code  
maintenance and programmer productivity as ObjC's features.

As of multiple inheritance, I usually use composite objects in ObjC.  To build  
a SavePanel you don't inherit from a button and from a window you use a button  
(i.e. a button that says Save and another for Cancel) object and a window (or  
panel) object.  The window will contain a button object, making it a composite  
object.  It's cleaner.  If you find a case where composite objects do not  
solve your problem and you have to use multiple inheritance let me know 'cause  
I'm still looking for a practical example.

That's why I like ObjC++.  But to me:

	 ObjC >> C++ 

where >> means "much greater than."  I'm not being religious, just  
"Objective."  Keep the one you like better!

--
Ricardo J. Parada
Pencom Software