From: <tomas@tuxteam.de>
To: 26221@debbugs.gnu.org
Subject: bug#26221: (define function nil should work in 2.2
Date: Fri, 24 Mar 2017 10:19:25 +0100 [thread overview]
Message-ID: <20170324091925.GA6245@tuxteam.de> (raw)
In-Reply-To: <BN6PR10MB17292650DB2FFE0FA2C9CE70A63F0@BN6PR10MB1729.namprd10.prod.outlook.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Mar 23, 2017 at 07:59:04PM +0000, Joshua Branson wrote:
>
> I can confirm this bug. Eshell accepts (defun hello nil (print “Hello")) And (hello) works properly.
>
> M-x guiler
>
> ,languages elisp
>
> (defun hello nil (print “Hello”)) doesn’t work.
>
> Joshua
>
> P.S. I didn’t even know (define function nil …) was a thing in elisp land.
No, no. It's not (defun nil) -- it's (defun foo nil ...), which, if you squint a
bit is the same (in Lisp!) as (defun foo () ...) -- defining function foo with
an empty argument list. This is a perfectly respectable thing to do.
That's because, for Lisp, nil, '() and false are all one and the same. Scheme
is pickier here, and I'd imagine that this is the reflection of one of those
translation pains. But I don't know enough about Guile's elisp implementation
to be sure (ah, I wish I had the time for that...)
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAljU5J0ACgkQBcgs9XrR2kY2SACffmA4jJ06fft6EBCbhm3m7Zwj
8Y8AnitudhEOZQjCzsa/tu29vFtNEFhZ
=0umF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-03-24 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 21:48 bug#26221: (defun function nil should work in 2.2 Jean Louis
2017-03-23 19:59 ` bug#26221: (define " Joshua Branson
2017-03-24 9:19 ` tomas [this message]
2021-05-19 11:52 ` bug#26221: (defun function nil ...) " Taylan Kammer
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170324091925.GA6245@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=26221@debbugs.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).