Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!news.duke.edu!godot.cc.duq.edu!hudson.lm.com!netline-fddi.jpl.nasa.gov!elroy.jpl.nasa.gov!lll-winken.llnl.gov!ames!ictv!tmh
From: tmh@ictv.com (Todd Hoff)
Subject: Re: Smalltalk has yet another 7-1 productivity advantage story ...
Message-ID: <1995Jan30.221532.16900@ictv.com>
Organization: /import/news/lib/organi[sz]ation
References: <3ge7r6$nti@news1.delphi.com> <3gegq2$sg4@falcon.ccs.uwo.ca> <1995Jan28.232519.4044@ictv.com> <791485940marten.marten@feki.toppoint.de>
Date: Mon, 30 Jan 1995 22:15:32 GMT
Lines: 28

In article <791485940marten.marten@feki.toppoint.de>,
Marten Feldtmann <marten@feki.toppoint.de> wrote:
>In article <1995Jan28.232519.4044@ictv.com> tmh@ictv.com (Todd Hoff) writes:
>
>>This would be my guess. 5 of the 7 points increase because of the
>>interpreter, 1 point because of the class library, maybe fractional
>>points for the lack of typedness although type safety isn't usually 
>>a slowdown for experienced C++ programmers, and the rest in memory 
>>management.
>
> "One" point for the class library ? ... Why at all do we speak about
>reusability ? :-)
>

Well i use rogue wave, database libraries, and GUI libraries so i do
have class libraries worth using. If i didn't then more points would
have been accorded.

What i sorely miss is an interpreter! 

> Only a fractional point for memory management ???

I would definitely use GC if it was available but it in my
experience memory management, using C++, hasn't been that big a problem.
Using C is a totally different issue. C++'s finalization through
destructors make resource deallocation of all types relatively simple. 
At the end of the day i do have some leaks but they are easily found. Most 
of the other memory problems are solved by clear statements of policy.
