home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.lisp.mcl
- Path: sparky!uunet!spool.mu.edu!yale.edu!jvnc.net!newsserver.jvnc.net!gmd.de!qw3!thomas
- From: thomas@gmd.de (Tom Gordon, I3.KI 2665)
- Subject: Re: MCL support for MOP
- Message-ID: <1993Jan9.091155.12279@gmd.de>
- Sender: news@gmd.de (USENET News)
- Nntp-Posting-Host: qw3
- Reply-To: thomas@gmd.de
- Organization: GMD, Sankt Augustin, Germany.
- References: <9301082050.AA28536@cambridge.apple.com>
- Date: Sat, 9 Jan 1993 09:11:55 GMT
- Lines: 28
-
- In article AA28536@cambridge.apple.com, bill@cambridge.apple.com (Bill St. Clair) writes:
- ...
- > We'll probably be
- > looking into a few ways to reduce the size of MCL (though probably
- > not for 2.1). Some ideas are:
- ...
- > 3) One or more shared libraries for the different pieces of MCL.
- > This will allow small MCL applications at the expense of some
- > large inits.
-
- Are shared libraries supported by the Mac OS?
-
- The WCL implementation of Common Lisp on Sparcs uses shared libaries
- very effectively, and my feeling is that this approach adequately
- solves the problem of not being able to decide what parts of the Common
- Lisp language and development environment are required by the
- application: Just deliver the whole system as a shared library and
- let anything required be loaded on demand.
-
- The only disadvantage I'm aware of is the the library takes up space on
- secondary storage, but this is not often a practical problem today.
-
- ---
- Thomas F. Gordon
- GMD, FIT; Artificial Intelligence Research Division
- 5205 Sankt Augustin 1 / Germany
- email: thomas.gordon@gmd.de; phone: (+49 2241) 14-2665
-
-