Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!hub!6600pete
From: 6600pete@hub.UUCP
Newsgroups: comp.sys.mac.programmer
Subject: Re: Segmentation (was Re: ARRGH (Strings and things))
Message-ID: <2842@hub.UUCP>
Date: 2 Nov 89 03:22:18 GMT
References: <8877@hoptoad.uucp>
Sender: news@hub.UUCP
Lines: 32

From article <8877@hoptoad.uucp>, by tim@hoptoad.uucp (Tim Maroney):
> In article <2825@hub.UUCP> 6600pete@hub.UUCP writes:
>>This would be a good article for Macker. How to use UnloadSeg safely. It would
>>cover
>>           o  when to do it
>>           o  what to do in the rest of the code to make sure you don't access
>>              any globals accessed while their segment is swapped out
> 
> But this question
> is (I don't know how to phrase this tactfully) silly.  Globals and
> segmentation have absolutely nothing to do with each other. 

You're right, of course. It was something I worried about when I
first started dragging units around in the Lightspeed Pascal project
window. I should have phrased it better.

> [ answer to the question about segmentation vs. globals ]

You sound like someone who is quite capable of writing and article on the
subject. Why don't you?

>>           o  how to make sure there will always be space to load a swapped-out
>>              segment.
> 
> This is a bit more perceptive.  Answer is: [ the answer ]

Hey! Save this for the article. Now your readers have lost X amount of interest
in the answer because they've seen a capsulized version already.
Pete Gontier   : pete@cavevax.ucsb.edu; outgoing .UUCP addresses bounce
Editor, Macker : Online Macintosh Programming Journal; mail for subscription
Hire this kid  : Mac, DOS, C, Pascal, asm, excellent communication skills
Underground    : Internet BBS via rlogin 128.11.41.100 -l bbs