Path: utzoo!mnetor!uunet!husc6!mit-eddie!zrm
From: zrm@eddie.MIT.EDU (Zigurd R. Mednieks)
Newsgroups: comp.sys.mac
Subject: Re: LSC, Mac limitations?
Message-ID: <8158@eddie.MIT.EDU>
Date: 12 Feb 88 15:07:48 GMT
References: <1161@hao.ucar.edu> <981@cadre.dsl.PITTSBURGH.EDU>
Reply-To: zrm@eddie.MIT.EDU (Zigurd R. Mednieks)
Organization: MIT, EE/CS Computer Facilities, Cambridge, MA
Lines: 28
Keywords: 32K limit, dynamic memory alloc.

In article <981@cadre.dsl.PITTSBURGH.EDU> km@cadre.dsl.pittsburgh.edu.UUCP (Ken Mitchum) writes:
>In article <1161@hao.ucar.edu> bill@hao.ucar.edu (Bill Roberts) writes:
>
>it was allocated on the stack, or through a call such as malloc(), it will
>contain garbage. Try calloc(), or set the field yourself.

Fer gosh sakes, use the Mac Toolbox memory managment. Especially if
you are managing big chunks of memory, and have dynamic requirements
through the course of running the program. The Mac Memory Manager has
far more powerful and efficient ways of handling memory allocation and
compaction than the standard Unix library has.

Another reason for using the Toolbox is reliability. Through version
2.13 of LSC there had been a major brain bubble in the Unix
compatible realloc function. It seems that compared to the very high
reliability of the rest of the product, the Unix compatibity libraries
are a weak point. Furthermore, since the Toolbox is the same
everywhere, and the Unix libraries are implemented separately in every
Mac development environment that has them, you are better off sticking
to the Toolbox if you ever change your mind about compilers (or
languages, for that matter).

-Zigurd
-- 
------------------------------------------------------------------------
Zigurd Mednieks		   MURSU Corporation		(617)424-0146
			   25 Exeter Street
			   Boston, MA 02116