Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!apple!well!svc
From: svc@well.UUCP (Leonard Rosenthol)
Newsgroups: comp.sys.mac.programmer
Subject: Segmentation (was Re: ARRGH (Strings and things))
Summary: You've got to be kidding, Tim!
Message-ID: <14386@well.UUCP>
Date: 31 Oct 89 17:46:27 GMT
References: <16004@netnews.upenn.edu> <8835@hoptoad.uucp> <16420@dartvax.Dartmouth.EDU> <8852@hoptoad.uucp>
Reply-To: svc@well.UUCP (Leonard Rosenthol)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 25

In article <8852@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>In article <8835@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) writes:
>>The moral: watch out for traps that require glue or put the glue in a 
>>segment that is never unloaded.
>
>I get a different moral out of this -- don't unload segments.  I use so
>many function pointers in my code that it's impossible anyway, so I
>don't have this problem.  As far as I'm concerned, UnloadSeg was
>relevant only to the Mac 128K....
>
	Are you serious, Tim?!?!?  UnloadSeg is as useful today (maybe even
more so) than it was back in the days of the 128K Mac...By using UnloadSeg and
keeping careful watch of which segs get used the most to keep them around and
possibly preloaded one is able to not only get lots of code into very small
MF partitions but can also keep their heap from getting fragmented.
	I think more programmers should start using UnloadSeg so that we can
have more small partition applications and therefore have more and more of them
running - sure I know about virtual memory, but I prefer the real thing!
So get with it folks - there is such as thing as UnloadSeg - USE IT!!!

-- 
+--------------------------------------------------+
Leonard Rosenthol        |  GEnie : MACgician
Lazerware, inc.          |  MacNet: MACgician
UUCP: svc@well.UUCP      |  ALink : D0025