unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Neil Jerram <neil@ossau.uklinux.net>,
	guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: macros, procedure->macro
Date: 15 Jul 2002 22:48:38 +0200	[thread overview]
Message-ID: <agvci0$p0$2@main.gmane.org> (raw)
In-Reply-To: <Pine.GSO.4.05.10207142321410.23724-100000@sallust.ida.ing.tu-bs.de>

Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:

>   (define-macro (foo x) `(list ,(bar x) ,x))
>   (define-macro (bar x) `(* ,x ,x))
> will work, because the macro definition will not be expanded.

Careful, Dirk. :) The term 'macro definition' is not really helpful
here, I think.  On the lowest level, a macro can be thought of as an
ordinary function that is called during compilation.  In order to run
this function, the macros that it uses must be expanded, like in any
other function.  The literal data structures that are embedded in the
function are not expanded, of course (just as they aren't for any
other function).

However, a 'quasi-quote' form is not a literal data structure, while
'quote' is.  'foo' from above is equivalent to

    (define-macro (foo x) (list 'list (bar x) x))

Thus, the function of the 'foo' macro makes use of the 'bar' macro,
which therefore needs to be defined when the compiler macro-expands
'foo's function, which might be just after it reads it in.  Had it
been

    (define-macro (foo x) (list 'list '(bar x) x))

then '(bar x)' would be a literal data structure and the definition
for 'bar' would be needed when the 'foo' macro is expanded, which
happens probably after 'bar' has been defined.


(Dirk, I don't think you need this detailed lecturing, but I couldn't
stop myself.)

_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


       reply	other threads:[~2002-07-15 20:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.05.10207142321410.23724-100000@sallust.ida.ing.tu-bs.de>
2002-07-15 20:48 ` Marius Vollmer [this message]
2002-07-15 22:42 ` macros, procedure->macro Neil Jerram
     [not found] <m3znws4nr2.fsf@laruns.ossau.uklinux.net>
2002-07-16 22:00 ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207130841180.21201-100000@sallust.ida.ing.tu-bs.de>
2002-07-14 15:23 ` Neil Jerram
2002-07-14 21:35   ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207131148030.21457-100000@sallust.ida.ing.tu-bs.de>
2002-07-13 18:38 ` Marius Vollmer
     [not found] <Pine.GSO.4.05.10207102338290.16926-100000@sallust.ida.ing.tu-bs.de>
2002-07-13  9:53 ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207102158440.16653-100000@sallust.ida.ing.tu-bs.de>
2002-07-13  0:09 ` Neil Jerram
     [not found] ` <m3d6ts7akl.fsf@laruns.ossau.uklinux.net>
2002-07-13  2:36   ` Clinton Ebadi
2002-07-13  6:53   ` Dirk Herrmann
     [not found]   ` <200207122236.56581.unknown_lamer@unknownlamer.org>
2002-07-14 15:23     ` Neil Jerram
     [not found]     ` <m3r8i65o6a.fsf@laruns.ossau.uklinux.net>
2002-07-14 16:26       ` Marius Vollmer
     [not found]       ` <87fzymff8b.fsf@zagadka.ping.de>
2002-07-15  6:03         ` Rob Browning
     [not found] <Pine.GSO.4.05.10207102138580.16653-100000@sallust.ida.ing.tu-bs.de>
2002-07-10 20:08 ` Marius Vollmer
     [not found] <m3d6tv99dp.fsf@laruns.ossau.uklinux.net>
2002-07-10 20:03 ` Dirk Herrmann
     [not found] <87hej7mlc3.fsf@zagadka.ping.de>
2002-07-10 19:57 ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207100709220.15376-100000@sallust.ida.ing.tu-bs.de>
2002-07-10 19:31 ` Marius Vollmer
     [not found] <Pine.GSO.4.05.10207100727490.15376-100000@sallust.ida.ing.tu-bs.de>
2002-07-10 10:15 ` Neil Jerram
     [not found] <m3fzysa9fe.fsf@laruns.ossau.uklinux.net>
2002-07-10  5:46 ` Dirk Herrmann
     [not found] <87ptxwdamm.fsf@zagadka.ping.de>
2002-07-10  5:21 ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207082223400.12632-100000@sallust.ida.ing.tu-bs.de>
2002-07-09 18:22 ` Marius Vollmer
     [not found] <Pine.GSO.4.05.10207082202540.12632-100000@sallust.ida.ing.tu-bs.de>
2002-07-09 18:13 ` Marius Vollmer
     [not found] <87r8if77a6.fsf@zagadka.ping.de>
2002-07-08 20:31 ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207042204110.5534-100000@sallust.ida.ing.tu-bs.de>
2002-07-07 18:15 ` Marius Vollmer
2002-07-08 20:23   ` Dirk Herrmann
2002-07-10 21:54   ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207032208310.27679-100000@sallust.ida.ing.tu-bs.de>
2002-07-07 17:54 ` Marius Vollmer
     [not found] <Pine.GSO.4.05.10207032204140.27679-100000@sallust.ida.ing.tu-bs.de>
2002-07-04 20:16 ` Dirk Herrmann
     [not found] <87k7ofb0h2.fsf@raven.i.defaultvalue.org>
2002-07-03 20:24 ` Dirk Herrmann
     [not found] <87adpbxfio.fsf@zagadka.ping.de>
2002-07-03 20:11 ` Dirk Herrmann
     [not found] <200207012220.PAA08054@onyx.he.net>
2002-07-03 20:08 ` Dirk Herrmann
     [not found] <Pine.GSO.4.05.10207012134500.15843-100000@sallust.ida.ing.tu-bs.de>
2002-07-01 20:27 ` Thien-Thi Nguyen
2002-07-03 20:02   ` Dirk Herrmann
2002-07-01 21:30 ` Rob Browning
2002-07-01 22:14 ` Marius Vollmer
2002-07-01 22:17 ` Gary Houston
2002-07-09 21:16 ` Neil Jerram
2002-07-01 19:56 Dirk Herrmann

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='agvci0$p0$2@main.gmane.org' \
    --to=mvo@zagadka.ping.de \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).