all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marco Antoniotti <marcoxa@cs.nyu.edu>
Subject: Re: Need general info on common lisp, opinions sought
Date: 03 Oct 2002 12:59:08 -0400	[thread overview]
Message-ID: <y6cr8f7laqr.fsf@octagon.valis.nyu.edu> (raw)
In-Reply-To: 9e8ebeb2.0210030436.7d87eee@posting.google.com


gnuist007@hotmail.com (gnuist) writes:

> Is it good to have the following line in .emacs file?
> (require 'cl)

I have it, although I think to remember that RMS disagrees.
If you are using some (X)Emacs packages you are bound to get a
top-level (require 'cl) anyway,  so I would not worry too much.

> Is it going to cause any tradeoff or only pure additions?

Mostly pure additions.  It definitively helps in the construction of
packages.  E.g. ELisp does not have `defstruct': you get that with the
CL package.

> How is common lisp different from emacs lisp?

There is one fundamental difference and a lot of big, yet not so
fundamental ones IMHO.  The main one is that CL is "statically
scoped", ELisp is "dynamically scoped".

Other differences are

CL has packages (read "modules" or "namespaces" - somethign that was
somewhat re-invented for Guile).

CL is "general purpose".  ELisp is "general purpose within the
confines of (X)Emacs" (of course (X)Emacs is the "total application",
but that is another story).

CL has provision for very efficient numerics and it is compiled to
native assembly on your machine.

> Where is the documentation on linux system?

`C-h i' is your friend :)  For CL start off at http://www.alu.org.

> Is it more than it or less than emacs lisp?

They serve different purposes.  If you need to extend (X)Emacs then
you should go with it.  If you need to do more generic programming
which required speed, then you should go with CL.

> Which should I use and why? I need info on people's taste on this
> subject.

They serve different purposes.  ELisp and CL are very simular.  If you
put (require 'cl) in your .emacs file, then you can write code that is
very much like CL code. Of course YMMV.

> Opinions sought!

As long as you know mine are worth only .02E :)

Cheers

-- 
Marco Antoniotti ========================================================
NYU Courant Bioinformatics Group        tel. +1 - 212 - 998 3488
715 Broadway 10th Floor                 fax  +1 - 212 - 995 4122
New York, NY 10003, USA                 http://bioinformatics.cat.nyu.edu
                    "Hello New York! We'll do what we can!"
                           Bill Murray in `Ghostbusters'.

  parent reply	other threads:[~2002-10-03 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 12:36 Need general info on common lisp, opinions sought gnuist
2002-10-03 13:23 ` huntingdon
2002-10-03 16:59 ` Marco Antoniotti [this message]
2002-10-03 18:36 ` Kaz Kylheku
2002-10-04  3:42 ` Christopher C. Stacy
2002-10-04  5:22   ` Christopher Browne

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

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

  git send-email \
    --in-reply-to=y6cr8f7laqr.fsf@octagon.valis.nyu.edu \
    --to=marcoxa@cs.nyu.edu \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.