[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why is tree-shaking hard?
- To: info-mcl@digitool.com
- Subject: Re: why is tree-shaking hard?
- From: barmar@nic.near.net (Barry Margolin)
- Date: 14 Mar 1995 18:20:28 -0500
- Organization: BBN Planet Corporation, Cambridge, MA
- References: <CONVERSE.95Mar2141828@orca.uchicago.edu>, <D5E7Et.7HL@midway.uchicago.edu>, <3k4gat$5sa@cantaloupe.srv.cs.cmu.edu>
- Sender: owner-info-mcl@digitool.com
In article <3k4gat$5sa@cantaloupe.srv.cs.cmu.edu> ram@cs.cmu.edu (Rob MacLachlan) writes:
>You can definitely get better control over size by not loading the stuff you
>don't need. One way that this has been done in Lisp is by "autoloading", but
>this isn't a complete solution, since it still requires as much or more disk
>space, and may result in worse sharability in multi-user environments.
Multics Maclisp used memory mapping (via the dynamic linker) to access the
code sections of compiled files loaded with LOAD. It seems that a similar
mechanism could be implemented in modern Unix Lisps.
--
Barry Margolin
BBN Planet Corporation, Cambridge, MA
barmar@near.net