From: Drew Adams <drew.adams@oracle.com>
To: Daniel Colascione <dancol@dancol.org>,
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 11:44:21 -0700 (PDT) [thread overview]
Message-ID: <172ea415-25d9-48d8-bc98-8017ff5ff332@default> (raw)
In-Reply-To: <5356B15B.7020802@dancol.org>
> 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.)
next prev parent reply other threads:[~2014-04-22 18:44 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 [this message]
2014-04-22 19:23 ` Daniel Colascione
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
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=172ea415-25d9-48d8-bc98-8017ff5ff332@default \
--to=drew.adams@oracle.com \
--cc=dancol@dancol.org \
--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 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).