From ... Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!134.222.94.5!npeer.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: exported package (was Re: Free software) References: <3b97d110_1@news.newsgroups.com> <87elpjn19q.fsf@nkapi.internal> <3208931568084195@naggum.net> <8766atq0j6.fsf_-_@Astalo.y2000.kon.iki.fi> Mail-Copies-To: never From: Erik Naggum Message-ID: <3208959625340667@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Sep 2001 17:40:26 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader2.kpnqwest.net 999970826 193.71.66.49 (Sat, 08 Sep 2001 19:40:26 MET DST) NNTP-Posting-Date: Sat, 08 Sep 2001 19:40:26 MET DST Xref: archiver1.google.com comp.lang.lisp:15960 * Kalle Olavi Niemitalo > What is an exported package? A package documented with its exported symbols and intended for others to use. Any serious implementation will need housekeeping or internal packages that they do not publish any documentation for. > Can a Common Lisp program export a package? No, but a vendor can choose to document and tell you about a package, or choose to withhold such information. ///