unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sam Steingold <sds@gnu.org>
Subject: Re: Is it better to use eLISP or Common LISP?
Date: Mon, 20 Oct 2003 16:37:10 -0400	[thread overview]
Message-ID: <uad7vbq89.fsf@gnu.org> (raw)
In-Reply-To: 1066674163.4152.13.camel@syr-24-59-77-252.twcny.rr.com

> * Dan Anderson <qna@znguwhaxvrf.pbz> [2003-10-20 14:22:43 -0400]:
>
> I am thinking of hacking some LISP for a project manager.  I know that I
> can either use Emacs LISP or the eLISP file that interfaces with common
> LISP.  Since I'd be learning LISP for the first time, what would be best
> to do?  Also, are there any reasons why?

The choice is between "Emacs-Lisp" and "Common Lisp".

I recommend Common Lisp.

Emacs-Lisp is a largely obsolete dialect, defined by its unique
implementations (Emacs & XEmacs stem from the same codebase), unsuitable
for large projects (even though many large projects indeed have been
done in it!)

Common Lisp is a modern standard language (actually, it was the first OO
language to receive an ANSI standard) with several high quality
implementations.

details: <http://www.podval.org/~sds/tool.html>

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
MS Windows: error: the operation completed successfully.

  reply	other threads:[~2003-10-20 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 18:22 Is it better to use eLISP or Common LISP? Dan Anderson
2003-10-20 20:37 ` Sam Steingold [this message]
     [not found] ` <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org>
2003-10-21 11:09   ` Phillip Lord
2003-10-21 14:36     ` Dan Anderson
     [not found]     ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org>
2003-10-21 14:53       ` Phillip Lord
2003-10-22  8:23       ` Tim X

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uad7vbq89.fsf@gnu.org \
    --to=sds@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).