From: Daniel Colascione <dancol@dancol.org>
To: Drew Adams <drew.adams@oracle.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117002: Correctly treat progn contents as toplevel forms when byte compiling
Date: Tue, 22 Apr 2014 12:23:36 -0700 [thread overview]
Message-ID: <5356C1B8.4070007@dancol.org> (raw)
In-Reply-To: <172ea415-25d9-48d8-bc98-8017ff5ff332@default>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On 04/22/2014 11:44 AM, Drew Adams wrote:
>> That said, the CL way is much better. It's conceptually simpler to say
>> that defmacro at toplevel is well-defined (progn contents being
>> considered "toplevel") and everything else is undefined than to try to
>> support this defmacro stuff in *all* contexts and run into the exciting
>> corner inherent in your approach...
>
> Are you saying that in CL if defmacro is used elsewhere than at top level
> it is not well-defined? That doesn't sound right to me.
>
> (Apologies if I misunderstand. If so, or if irrelevant, please ignore.)
Compilers appear to differ. Consider the code below:
(defun foo ()
(defmacro bar () 1)
(bar))
(format t "~s" (foo))
SBCL and ECL both signal an error. CLISP compiles the file, substituting
(bar) with 1, then complains when calling foo that bar is redefined. The
SBCL and ECL behavior is what I'd expect from reading the spec, but
maybe I misunderstood something.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2014-04-22 19:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WcAcP-0006zy-MJ@vcs.savannah.gnu.org>
2014-04-21 15:09 ` [Emacs-diffs] trunk r117002: Correctly treat progn contents as toplevel forms when byte compiling Stefan Monnier
2014-04-21 17:44 ` Daniel Colascione
2014-04-21 22:09 ` Stefan Monnier
2014-04-21 22:29 ` Daniel Colascione
2014-04-22 2:09 ` Stefan Monnier
2014-04-22 2:21 ` Daniel Colascione
2014-04-22 4:25 ` Stefan Monnier
2014-04-22 4:46 ` Daniel Colascione
2014-04-22 15:06 ` Stefan Monnier
2014-04-22 17:22 ` Daniel Colascione
2014-04-22 18:13 ` Daniel Colascione
2014-04-22 18:37 ` Stefan Monnier
2014-04-22 19:08 ` Daniel Colascione
2014-04-22 18:44 ` Drew Adams
2014-04-22 19:23 ` Daniel Colascione [this message]
2014-04-22 19:59 ` Drew Adams
2014-04-22 20:10 ` Daniel Colascione
2014-04-22 20:41 ` Drew Adams
2014-04-22 21:05 ` Daniel Colascione
2014-04-23 0:50 ` Stephen J. Turnbull
2014-04-22 18:29 ` Stefan Monnier
2014-04-22 15:20 ` Stefan Monnier
2014-04-22 17:04 ` Daniel Colascione
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=5356C1B8.4070007@dancol.org \
--to=dancol@dancol.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.