From: Gareth Rees <gareth.rees@pobox.com>
To: bug-gnu-emacs@gnu.org
Cc: Gareth Rees <gareth.rees@pobox.com>
Subject: Manual for `cl' package is out of date
Date: Tue, 23 Oct 2007 13:22:27 +0100 [thread overview]
Message-ID: <471DE783.6070006@pobox.com> (raw)
The manual for the `cl' package is out of date in a couple places.
Node "(cl)Porting Common Lisp" says:
* Reader macros. Common Lisp includes a second type of macro that
works at the level of individual characters. For example, Common
Lisp implements the quote notation by a reader macro called `'',
whereas Emacs Lisp's parser just treats quote as a special case.
Some Lisp packages use reader macros to create special syntaxes
for themselves, which the Emacs parser is incapable of reading.
The lack of reader macros, incidentally, is the reason behind
Emacs Lisp's unusual backquote syntax. Since backquotes are
implemented as a Lisp package and not built-in to the Emacs
parser, they are forced to use a regular macro named ``' which is
used with the standard function/macro call notation.
This has become a bit misleading: it's still true that Emacs Lisp lacks
reader macros but Emacs Lisp's backquote syntax is no longer "unusual"
because backquote is now handled in the reader. Maybe just delete the
second paragraph?
Further down in "(cl)Porting Common Lisp":
* Characters are distinct from integers in Common Lisp. The
notation for character constants is also different: `#\A' instead
of `?A'.
`?A' is now supported in Emacs.
Node "(cl)Top" offers this menu item:
* Lists:: `cadr', `sublis', `member*', `assoc*', etc.
The function `cadr' is no longer described in this node. The menu item
should mention `caddr' instead.
--
Gareth Rees
next reply other threads:[~2007-10-23 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 12:22 Gareth Rees [this message]
2007-10-23 12:41 ` Manual for `cl' package is out of date Andreas Schwab
2007-10-23 23:17 ` Gareth Rees
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=471DE783.6070006@pobox.com \
--to=gareth.rees@pobox.com \
--cc=bug-gnu-emacs@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 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.