Message from discussion
Why I can't use Lisp.
Path: archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-01!sn-xit-04!supernews.com!pd2nf1so.cg.shawcable.net!residential.shaw.ca!news3.calgary.shaw.ca.POSTED!not-for-mail
X-Trace-PostClient-IP: 24.80.253.172
Sender: stephen@anakin
Newsgroups: comp.lang.lisp
Subject: Re: Why I can't use Lisp.
References: <b295356a.0208011247.562f2f26@posting.google.com> <tp9lku80o054hebl04raid9oqm4i13ftfj@4ax.com> <871y9fj54f.fsf@meo-dipt.andreas.org> <aihgsq$n3a$1@luna.vcn.bc.ca> <87k7n7gci6.fsf@meo-dipt.andreas.org> <aijkee$in7$2@luna.vcn.bc.ca> <m3y9bmmscg.fsf@dino.dnsalias.com> <3D4D7533.2043284@dls.net>
From: step...@dino.dnsalias.com (Stephen J. Bevan)
Organization: just me at home
Message-ID: <m3heiamnvq.fsf@dino.dnsalias.com>
Lines: 18
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 04 Aug 2002 19:21:29 GMT
NNTP-Posting-Host: 24.69.255.206
X-Complaints-To: abuse@shaw.ca
X-Trace: news3.calgary.shaw.ca 1028488889 24.69.255.206 (Sun, 04 Aug 2002 13:21:29 MDT)
NNTP-Posting-Date: Sun, 04 Aug 2002 13:21:29 MDT
"Paul F. Dietz" <di...@dls.net> writes:
> "Stephen J. Bevan" wrote:
> > It remember when Le Lisp, Xlisp and Portable Standard Lisp used to be
> > mentioned/discussed in comp.lang.lisp. I haven't seen any mentioned
> > here in a while, let alone Cambridge Lisp. However, I still haven't
> > got used to thinking of ``Lisp'' as ``Common Lisp'' in this group
> > despite what the FAQ says. Note to myself to try harder :-)
>
> What about Autolisp?
My list above wasn't meant to be exclusive, it was just some of the
Lisps I used in the past and which were once discussed here. None of
them had a separate newsgroup devoted to them and so comp.lang.lisp
was a natural place to discuss them. Depending on exactly what the
issue was with Autolisp then comp.cad.autocad may or may not be a
better place to discuss it. If it was something generically Lispy
then comp.lang.lisp seems fine to me -- though perhaps not to others
given the warning in the FAQ.