Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!hsdndev!husc6!endor!siegel
From: siegel@endor.uucp (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Memory (was Re: Another THINK Pascal gotcha - "With" instance vars)
Message-ID: <5534@husc6.harvard.edu>
Date: 31 Jan 91 02:17:21 GMT
References: <1991Jan25.233122.2825@fennel.cc.uwa.oz.au> <48579@apple.Apple.COM> <15967@reed.UUCP>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 35

In article <15967@reed.UUCP> orpheus@reed.UUCP (P. Hawthorne) writes:

>    Even though it may be possible to pin down every time memory may get
>moved around, it takes a significant amount of thought and time to do so.

	In fact, it takes comparitively little of either, since all of the
traps that move memory are documented, and new ones are document as soon
as is practical. As for old ones suddenly starting to move memory, I doubt
that any action by Apple will cause this problem, since they rarely
break something so fundamental.

>    My largest problem with memory, now, is in overcoming the 32K limit on
>variables in Think Pascal. Right about now, I would kill or die to see the
>same attention that is being devoted to locking handles being devoted to
>dynamic length objects and arrays.
	
	Which 32K limitation? Variable size, local allocation, or global
allocation?

>    I can't reserve large block of memory without bombing, if I use it.
>Leave it alone and I never get a bad result. So maybe I'm overwriting the
>object identifier bytes at the end of the object. The manual has precious 

	The class ID is at the beginning of an object, not the end.
If you can be more specific about your crashes, that might lead us toward
a solution.

R.



 Rich Siegel	Symantec Languages Group  Internet: siegel@endor.harvard.edu

"...she's dressed in yellow, she says 'Hello, come sit next to me, you
fine fellow..."