Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!bingvaxu!sunybcs!boulder!stan!dce
From: dce@stan.UUCP (David Elliott)
Newsgroups: comp.sys.mac.programmer
Subject: Handling large applications as segments or using DAs
Message-ID: <659@salgado.stan.UUCP>
Date: 23 Mar 89 15:50:34 GMT
Reply-To: dce@stan.UUCP (David Elliott)
Organization: Solbourne Computer Inc., Longmont, Colorado
Lines: 23

I'm working on an application that is made up of several distinct
parts, only a couple of which need to be active at a given time.

The basic program reads and writes a specific file format, handles the
data storage, and displays the data.  In addition, there are modules
for aquiring new data, filtering the data, and modifying the data.
At any given time, only one of these special modules is needed.

Is there a way to segment my application so that I only keep the
code segments needed in memory?  I suspect that this application
is going to eventually have a lot of modules, so I'd like to be
able to pull them in as needed.

I guess what I'm really asking is how to do overlays with the Mac.

Alternatively, would it be possible to write the modules as desk
accessories and have them communicate with the main program through
temp files?  How easy is this to do, and what are the traps into
which I might fall?

-- 
David Elliott		...!pyramid!boulder!stan!dce
"Splish splash, I was rakin' in the cash"  -- Eno