From: Achim Gratz <Stromeko@NexGo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: Build fail with emacs 24.3.1
Date: Thu, 14 Mar 2013 08:26:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20130314T085704-386@post.gmane.org> (raw)
In-Reply-To: 87wqtalnlc.fsf@bzg.ath.cx
Bastien <bzg <at> altern.org> writes:
> One potential problem in the first test is the use of "parent" as the
> name of the symbol to pass to the macro... since this is the very same
> name than the macro second argument. At least this reminded me this
> section of Elisp manual:
I've actually tested this by renaming the macro arguments and no symbol
capturing seems to be involved via this path. The symbol is never used unquoted
in the macro expansion anyway.
> So... instead of fixing the macro calls in the tests, I've been
> wondering why using a macro for `org-export-define-derived-backend'
> and `org-export-define-backend' would be better?
I think that these are proper uses of macros since Nicolas is introducing
special syntax for defining a backend. In any case before anything is changed
we should know why this is happening at all.
Regards,
Achim.
next prev parent reply other threads:[~2013-03-14 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 7:39 Build fail with emacs 24.3.1 Neuwirth Erich
2013-03-13 11:58 ` Bastien
2013-03-13 12:53 ` Andreas Röhler
2013-03-13 12:56 ` Bastien
2013-03-13 20:07 ` Achim Gratz
2013-03-14 2:30 ` Bastien
2013-03-14 8:26 ` Achim Gratz [this message]
2013-03-14 11:26 ` Bastien
2013-03-14 12:28 ` Bastien
2013-03-14 19:09 ` Achim Gratz
2013-03-19 17:14 ` Bastien
2013-03-20 19:03 ` `org-export-define-backend' and its friends are now defuns (was: Build fail with emacs 24.3.1) Florian Beck
2013-03-20 22:58 ` `org-export-define-backend' and its friends are now defuns Bastien
2013-05-19 14:36 ` Build fail with emacs 24.3.1 Achim Gratz
2013-05-20 10:13 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2013-03-13 12:29 Susan Cragin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20130314T085704-386@post.gmane.org \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).