Article View: comp.lang.lisp.mcl
Article #638MCL Operating System
From: Henry Lieberman
Date: Thu, 21 Jan 1993 17:30
Date: Thu, 21 Jan 1993 17:30
17 lines
1351 bytes
1351 bytes
Actually, an even better idea is to call the MCL application an "init" and tell people that you have to put it in the Extensions folder inside the System Folder [no harm in that being there, is there?]. It's only about twice as big as the Quicktime init, and does lots more. Then call each fasl file an "application", and marvel at how small the applications are. But seriously, folks, why should the "size" of the MCL application matter at all? If System 7 virtual memory works correctly [and here is where I may be assuming too much], the virtual memory system should dynamically decide what you need to keep in memory and what you don't. Virtual memory is a dynamic "tree shaker", and thus should be able to do better than any static tree shaker could ever do, and no problems with EVAL, etc. Henry Lieberman
Technical Details
Message-ID:
<9301211730.AA09884@media.mit.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!elroy.jpl.nasa.gov!ames!data.nas.nasa.gov!taligent!apple!cambridge.apple.com!lieber@media.mit.eduReferences:
Peter Hendrickson's message of 15 Jan 93 20:01:22 GMT <1993Jan15.200122.7395@netcom.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!elroy.jpl.nasa.gov!ames!data.nas.nasa.gov!taligent!apple!cambridge.apple.com!lieber@media.mit.edu From: lieber@media.mit.edu (Henry Lieberman) Newsgroups: comp.lang.lisp.mcl Subject: MCL Operating System Message-ID: <9301211730.AA09884@media.mit.edu> Date: 21 Jan 93 17:30:33 GMT References: Peter Hendrickson's message of 15 Jan 93 20:01:22 GMT <1993Jan15.200122.7395@netcom.com> Sender: owner-info-mcl@cambridge.apple.com Lines: 17 Approved: comp.lang.lisp.mcl@Cambridge.Apple.C0M