From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: What Lisp capabilities are removed when packaged runtime Lisp programs are built using LW or ACL? References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3225253356742033@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Mar 2002 07:42:25 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1016264545 193.71.199.50 (Sat, 16 Mar 2002 08:42:25 MET) NNTP-Posting-Date: Sat, 16 Mar 2002 08:42:25 MET Xref: archiver1.google.com comp.lang.lisp:29151 * "Bruce Lester" | I am wondering what Lisp capabilities are removed when runtime Lisp | programs are built using LW or ACL. For ACL, that is basically up to you and your license agreement. | For example, if I created a program that used macros to generate CLOS | classes and method definitions, and built a runtime package, would the | program work without the LW or ACL development environments? Yes. Please note that Franz Inc has made their entire documentation set available on the Net. http://franz.com/support/documentation/ /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.