Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!ox.com!tbomb.ice.com!time From: time@tbomb.ice.com (Tim Endres) Newsgroups: comp.sys.mac.programmer Subject: WANTED: Discussions regarding code segment loading Message-ID: Date: 2 Sep 90 01:00:27 GMT Reply-To: time@tbomb.ice.com Organization: ICE Engineering, Inc. Lines: 17 X-Mailer: uMail - Mac Release: 0.1.3 Some time ago there was a discussion concerning code segments, and the religion regarding wether or not they should be locked down, and unpurgable, or if they should be dynamically loaded and unloaded. In the process of tightening down an application, I have realized that I am running into cases of a code segment being unloaded, with no hope of loading the thing in a full heap. When this happens, of course, things go bad. The only reasonable thing to do seems to load and lock down (after MoveHHi) all code segments (or at least those that are critical and could be called without the ability to check for their existence first). But this ties up precious memory. Does anyone have a distillation of the discussion concerning this topic? Anyone care to comment? Am I missing some obvious technique? tim. ------------------------------------------------------------- Tim Endres | time@ice.com ICE Engineering | uunet!ice.com!time 8840 Main Street | Whitmore Lake MI. 48189 | --- Disclaimed.