Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!udel!new
From: new@udel.EDU (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Standard File Requesters
Message-ID: <15219@louie.udel.EDU>
Date: 11 May 89 18:28:59 GMT
References: <0914.AA0914@amigash> <941@sactoh0.UUCP> <11583@well.UUCP> <UYNn=hy00VsfE2FI4k@andrew.cmu.edu> <1051@quintus.UUCP>
Sender: usenet@udel.EDU
Reply-To: new@udel.EDU (Darren New)
Distribution: na
Organization: University of Delaware
Lines: 14

In article <1051@quintus.UUCP> pds@quintus.UUCP (Peter Schachte) writes:
>But you're not going far enough, either.  By putting everything in one
>library, you either restrict its scope or burden the whole system with
>lots of code in memory when only a small part is needed.  Putting

Alternately, have everything in the library (or most everything) be a stub
that LoadSeg's another file and patches the stub. (Do I hear an echo? :-)
Then replacing the stub file could change portions of the library and allow 
low memory overhead. Problems: what if I don't have the memory to do the
LoadSeg? How to clean up when expunged? How to specify that more than
one routine is in the same file (like open file requester and save
file requester)? But these are fairly trivial things overall.

		- Darren New