Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!bu-cs!dartvax!dartmouth.edu
From: Jim.Matthews@dartmouth.edu (Jim Matthews)
Newsgroups: comp.sys.mac.programmer
Subject: Re: ARRGH (Strings and things)
Message-ID: <16420@dartvax.Dartmouth.EDU>
Date: 30 Oct 89 17:15:59 GMT
References: <16004@netnews.upenn.edu> <8835@hoptoad.uucp>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: Jim.Matthews@dartmouth.edu
Organization: Dartmouth College
Lines: 14

In article <8835@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) writes:
> 
> BlockMove doesn't touch the heap so it's safe to use this dereference
> even when mystringhandle is unlocked or purgeable (but not purged!)

A paranoid note: BlockMove doesn't move memory, but since it's an OS trap
most compilers get to it through glue. If that glue is in an unloaded
segment, then the act of *calling* BlockMove will move memory.

The moral: watch out for traps that require glue or put the glue in a 
segment that is never unloaded.
--
Jim Matthews
Dartmouth Software Development