From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: datatypes in Elisp Info: mention "things" for which there is no "thing" datatype - e.g. faces
Date: Thu, 23 Jun 2005 10:34:25 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICCEKFCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <jk3br9j8ao.fsf@glug.org>
while i agree that the documentation could make more distinction between
fundamental and composed (or "defined-by-conventional-use") types, i
figure that doing so might be a bad idea because it would constrain the
implementation.
since `facep' works like `functionp' (fsvo "like"), that should be what
programmers rely on. if in the future faces become fundamental, that
transition will be easier to handle if prior internals were left
unexposed (ignorance is bliss).
One of my concerns is that readers of the datatypes section will not know
that faces exist. This section is near the beginning of the manual, and it
can give the impression that it also presents all of the important
Emacs-Lisp objects.
At a minimum, I think it would help to mention that, although these are the
only datatypes, there are additional things of interest (like faces) that
are not listed here.
next prev parent reply other threads:[~2005-06-23 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 16:00 datatypes in Elisp Info: mention "things" for which there is no "thing" datatype - e.g. faces Drew Adams
2005-06-23 17:24 ` Thien-Thi Nguyen
2005-06-23 17:34 ` Drew Adams [this message]
2005-06-24 1:28 ` Miles Bader
2005-06-24 13:58 ` Drew Adams
2005-06-24 17:38 ` Kevin Rodgers
2005-06-24 18:41 ` Luc Teirlinck
2005-06-24 21:22 ` Luc Teirlinck
2005-06-24 22:16 ` Miles Bader
2005-06-24 5:36 ` Richard M. Stallman
2005-06-24 6:32 ` Kenichi Handa
2005-06-25 0:31 ` Richard M. Stallman
2005-06-24 13:58 ` datatypes in Elisp Info: mention "things" for which there is no"thing" " Drew Adams
2005-06-24 14:21 ` datatypes in Elisp Info: mention "things" for which there is no "thing" " 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=DNEMKBNJBGPAOPIJOOICCEKFCJAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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).