Article View: comp.lang.lisp.mcl
Article #730RE: Reducing Size of MCL applications
From: "pierce"
Date: Mon, 11 Jan 1993 04:05
Date: Mon, 11 Jan 1993 04:05
22 lines
1465 bytes
1465 bytes
>>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. This discussion seems to be implying that size of MCL applications is the only issue preventing the rapid delivery of commercial applications in MCL. Let me emphasize that I believe the ability to integrate existing foreign C++ libraries and application frameworks such as Bedrock with MCL code is equally important. The Lisp community should not have to reinvent everything and MCL should not prevent MCL developers from benefiting from existing foreign code. Supporting hybrid application development would make MCL applications smaller and allow MCL developers to work with other programming team members or other programming teams who have chosen C++ without having to convince them to switch to Lisp. -Jonathan Pierce pierce@Vitro.com
Technical Details
Message-ID:
<9301111603.AA20414@brazil.cambridge.apple.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!apple!goofy!cambridge.apple.com!pierce@at-mail-server.vitro.comShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!apple!goofy!cambridge.apple.com!pierce@at-mail-server.vitro.com
From: pierce@at-mail-server.vitro.com ("pierce")
Newsgroups: comp.lang.lisp.mcl
Subject: RE: Reducing Size of MCL applications
Message-ID: <9301111603.AA20414@brazil.cambridge.apple.com>
Date: 11 Jan 93 04:05:15 GMT
Sender: info-mcl-request@cambridge.apple.com
Lines: 22
Approved: comp.lang.lisp.mcl@Cambridge.Apple.C0M