From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Why is booleanp defined this way?
Date: Sat, 18 Apr 2015 03:23:22 +0200 [thread overview]
Message-ID: <87fv7ymdpx.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 871tjint39.fsf@debian.uxu
Emanuel Berg <embe8573@student.uu.se> writes:
> Are you saying (not (not x)) generates more efficient
> byte-code? I hate to break it to you, but the
> Commodore 64 demo era is long gone :)
That's what I'm saying, in the case of a lisp VM (emacs lisp, clisp).
In the case of a not too dumb native compiler, both should generate the
same native code.
>>> So I think `booleanp' shouldn't be thought of as
>>> a normalizer but rather as a type predicate, much
>>> like them `stringp', `integerp', and so on.
>>
>> Of course. That's what the "p" in "booleanp" means!
>
> If that is "of course" then what are we talking about?
I'm just stating that you are stating the obvious.
Obviously :-)
--
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
next prev parent reply other threads:[~2015-04-18 1:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 20:34 Why is booleanp defined this way? Marcin Borkowski
2015-04-17 20:49 ` Jorge A. Alfaro-Murillo
[not found] ` <mailman.962.1429303822.904.help-gnu-emacs@gnu.org>
2015-04-17 23:06 ` Emanuel Berg
2015-04-18 0:41 ` Pascal J. Bourguignon
2015-04-18 1:06 ` Emanuel Berg
2015-04-18 1:23 ` Pascal J. Bourguignon [this message]
2015-04-18 7:44 ` Marcin Borkowski
2015-04-18 8:37 ` Stefan Nobis
2015-04-19 23:15 ` Emanuel Berg
2015-04-18 2:37 ` Drew Adams
2015-04-18 6:13 ` Tassilo Horn
[not found] <mailman.946.1429302909.904.help-gnu-emacs@gnu.org>
2015-04-17 20:55 ` Pascal J. Bourguignon
2015-04-17 23:20 ` Barry Margolin
2015-04-17 23:30 ` Emanuel Berg
2015-04-18 0:43 ` Pascal J. Bourguignon
2015-04-18 3:13 ` Barry Margolin
2015-04-18 3:12 ` Barry Margolin
2015-04-18 2:01 ` Rusi
2015-04-18 2:23 ` Emanuel Berg
2015-04-18 2:33 ` Rusi
2015-04-18 2:55 ` Emanuel Berg
2015-04-18 3:11 ` Barry Margolin
2015-04-18 3:35 ` Rusi
2015-04-18 4:56 ` Barry Margolin
2015-04-19 23:08 ` Emanuel Berg
2015-04-19 23:00 ` Emanuel Berg
2015-04-18 21:24 ` Emanuel Berg
2015-04-18 7:52 ` Marcin Borkowski
[not found] ` <mailman.997.1429343558.904.help-gnu-emacs@gnu.org>
2015-04-18 12:43 ` Rusi
2015-04-18 4:09 ` Pascal J. Bourguignon
2015-04-18 5:00 ` Rusi
2015-04-18 3:50 ` Pascal J. Bourguignon
2015-04-18 5:03 ` 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=87fv7ymdpx.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-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.
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).