Newsgroups: alt.lang.design,comp.lang.c++,comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!howland.reston.ans.net!pipex!uunet!franz.com!franz!smh
From: smh@Franz.COM (Steve Haflich)
Subject: Re: Comparing productivity: LisP against C++ (was Re: Reference Counting)
In-Reply-To: rj@wariat.org's message of 31 Dec 1994 07:13:20 GMT
Message-ID: <SMH.94Dec31022415@vapor.Franz.COM>
Sender: news@franz.com
Nntp-Posting-Host: vapor
Organization: Franz Inc., Berkeley, CA
References: <D16Ho3.4BE@lcpd2.SanDiegoCA.NCR.COM> <3e2bj6$43a@network.ucsd.edu>
	<3e30ag$ar1@wariat.wariat.org>
Date: Sat, 31 Dec 1994 10:24:15 GMT
Lines: 14
Xref: glinda.oz.cs.cmu.edu comp.lang.c++:105385 comp.lang.lisp:16218

In article <3e30ag$ar1@wariat.wariat.org> rj@wariat.org (Robert J. Brown) writes:

   From: rj@wariat.org (Robert J. Brown)

   : 	"Memory leaks are relatively easy to deal with as long as you
   : 	 use free() when the data pointed to will no longer be used."

   C and C++ programmers are rather proud of themselves in thinking that they
   will always know when an object is no longer being referenced by anything
   else, but the dangling reference is one of the most notorious and hard to
   find class of bugs in these programming languages!
   They just do not believe in garbage collection ...

True.  When your hammer is C++, everything begins to look like a thumb.
