Xref: utzoo comp.lang.c++:3632 comp.lang.eiffel:263
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!cs.utexas.edu!uunet!mcvax!kth!sunic!enea!sommar
From: sommar@enea.se (Erland Sommarskog)
Newsgroups: comp.lang.c++,comp.lang.eiffel
Subject: Re: Eiffel vs. C++ -- Let's drop the garbage collection arguments
Message-ID: <34@enea.se>
Date: 11 Jun 89 21:12:44 GMT
Organization: Enea Data AB, Sweden
Lines: 17

Larry Campbell (campbell@redsox.UUCP) writes:
>The problem is, neither gets the choice.  In C++, you CANNOT have garbage
>collection.  In Eiffel you cannot PREVENT garbage collection.  Why not
>give the programmer a choice?

I don't have my OOSC around at the moment, but far as I recall Eiffel
does give you a choice. You can turn off garbage collection if you
absolutely have to. And calls corresponding to manually free memory
are also available. But you are certainly not encouraged to use them.
My apologies if I'm wrong on this point.

I don't speak C++, but an object-oriented langauge without garbage
collection seem quite useless to me. Or rather: it's not really
an object-oriented langauge, just a more structured form of C.
-- 
Erland Sommarskog - ENEA Data, Stockholm - sommar@enea.se
Bowlers on strike!