From: Ken Olum <kdo@cosmos.phy.tufts.edu>
To: emacs-devel@gnu.org
Subject: Re: Declaring cl.el obsolete
Date: Thu, 23 May 2019 11:08:31 -0400 [thread overview]
Message-ID: <q52o93tw6mo.fsf@cosmos.phy.tufts.edu> (raw)
In-Reply-To: <m3ftp54l1p.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 23 May 2019 10:44:34 +0200)
If I understand things correctly, the important difference between cl
and cl-lib is that the former provides actual Common Lisp compatibility,
whereas the latter allows you to use some Common Lisp features by
renaming functions that are in Common Lisp but not in Emacs lisp by
adding "cl-". My goal is just to be able to write code without worrying
about which functions are in which language, so I would like to stick
with cl. Thus it seems to me that cl-lib provides different
functionality and doesn't render cl obsolete.
For whatever it's worth, some of the controversy here and in the
backquote discussion seems to arise from differences between people who
are Lisp programmers in the rest of their lives and those using it only
for emacs.
Ken
next prev parent reply other threads:[~2019-05-23 15:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 3:26 Declaring cl.el obsolete Stefan Monnier
2019-05-23 4:47 ` Eli Zaretskii
2019-05-23 10:28 ` Noam Postavsky
2019-05-23 14:20 ` Eli Zaretskii
2019-05-24 14:28 ` Stefan Monnier
2019-05-24 15:03 ` Eli Zaretskii
2019-05-24 16:22 ` Stefan Monnier
2019-05-23 8:44 ` Lars Ingebrigtsen
2019-05-23 8:50 ` Lars Ingebrigtsen
2019-05-23 17:03 ` Romanos Skiadas
2019-05-24 1:22 ` 조성빈
2019-05-25 20:12 ` Romanos Skiadas
2019-05-23 12:15 ` Stefan Monnier
2019-05-23 15:08 ` Ken Olum [this message]
2019-05-23 15:57 ` Sam Steingold
2019-07-23 15:07 ` Stefan Monnier
2019-07-23 16:29 ` Drew Adams
2019-07-23 16:55 ` Stefan Monnier
2019-08-06 8:02 ` Stefan Monnier
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=q52o93tw6mo.fsf@cosmos.phy.tufts.edu \
--to=kdo@cosmos.phy.tufts.edu \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).