Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!PT.CS.CMU.EDU!cadre!km
From: km@cadre.dsl.PITTSBURGH.EDU (Ken Mitchum)
Newsgroups: comp.sys.mac
Subject: Re: LSC Storage bugs
Keywords: LSC, malloc, bugs
Message-ID: <968@cadre.dsl.PITTSBURGH.EDU>
Date: 8 Feb 88 12:52:02 GMT
References: <5295@columbia.edu>
Reply-To: km@cadre.dsl.pittsburgh.edu.UUCP (Ken Mitchum)
Organization: Decision Systems Lab., Univ. of Pittsburgh, PA.
Lines: 19

In article <5295@columbia.edu> kearns@cs.columbia.edu writes:
>LSC  is a great product; I have noticed, though, that in most compilers the
>libraries are an afterthought, often delegated to inexperienced programmers.
>Especially with memory management routines this is bad.  (I found even
>worse problems in Aztec C's memory management, for example, several years ago)

Yes, I experienced the same problem, not just with the memory management
functions, but with other libary functions. The Lightspeed manual entry
reads just like the Unix manual entry, but you look at the library sources
and find entire features missing. The realloc() source simply calls
SetPtrSize(), without any attempt at moving the block if unsuccessful.

In all fairness, I have not yet sent Think, Inc. the $10 for the latest
library sources (2.15), and I assume that they have fixed things in the
latest libraries. However, the difference between the manual and th
sources is still irritating.

-ken mitchum
 univ of pgh DSL