Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!nntp.sei.cmu.edu!cis.ohio-state.edu!math.ohio-state.edu!howland.reston.ans.net!newsfeed.internetmci.com!news.kei.com!nntp.coast.net!torn!nott!cunews!dbuck
From: dbuck@superior.carleton.ca (Dave Buck)
Subject: Re: Garbage Collection ?
X-Nntp-Posting-Host: superior.carleton.ca
Message-ID: <DJMBs2.HvF@cunews.carleton.ca>
Sender: news@cunews.carleton.ca (News Administrator)
Organization: Carleton University, Ottawa, Canada
References: <INFO-CLS%95121116540159@vm.gmd.de> <DJH29H.BLs@cunews.carleton.ca> <4ar0m8$pop@news2.ios.com>
Date: Fri, 15 Dec 1995 08:04:50 GMT
Lines: 28

In article <4ar0m8$pop@news2.ios.com>, vlad <vlad@gramercy.ios.com> wrote:
>dbuck@superior.carleton.ca (Dave Buck) wrote:
>
>>In article <INFO-CLS%95121116540159@vm.gmd.de>,
>>Axel Berle  <POSMEC10%BRUFU.BitNet@pucc.PRINCETON.EDU> wrote:
>>>One aspect of C++ that I would like to comment is the problem of
>>>'garbage collection' in comparison with other languages like EIFEL.
>>>With C++ the programmer is fully responsible for object memory allocation
>>>and deallocation. 'Forgotten' objects result in memory leaks.
>
>>This is a serious and annoying problem in C++ 
>This is not a problem. It is a strength! The possiblity to be able to
>control memory allocation and deallocation is very usefull.

It's clear that most languages allow you to control memory allocation.
That's very useful.  Can you explain how it's useful being able to
control deallocation rather than letting a garbage collector do it?


David Buck
dbuck@ccs.carleton.ca

_________________________________
| David K. Buck                 |
| dbuck@ccs.carleton.ca         |
| The Object People             |
|_______________________________|

