From: isaac lewis <isaac.b.lewis@gmail.com>
To: 26955@debbugs.gnu.org
Subject: bug#26955: macroexpand: documentation and actual behavior differ
Date: Tue, 16 May 2017 04:48:12 -0400 [thread overview]
Message-ID: <CA+a_5chfsZPkFu=vZDUd+x_Jn_CJPq5LL_Ly5s-VVMgiRdio6Q@mail.gmail.com> (raw)
Guile version: 2.0.11
Machine type: x86_64-unknown-linux-gnu
===
Bug
===
The first 3 examples given in the documentation for 'macroexpand' in
section 9.4.2 do not expand to the printed results; for example
(macroexpand '(+ 1 2)) yields
=>
#<tree-il (apply (toplevel +) (const 1) (const 2))>
instead of
'(+ 1 2)
Moreover, the optional 'm' argument (see psyntax.scm: 2567) seems to
have no influence;
(equal? (macroexpand '(+ 1 2)) (macroexpand '(+ 1 2) 'e)
(macroexpand '(+ 1 2) 'c))
=>
#t
Sincerely,
Ikester
next reply other threads:[~2017-05-16 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 8:48 isaac lewis [this message]
2017-05-24 6:01 ` bug#26955: isaac lewis
2021-05-16 18:05 ` bug#26955: macroexpand: documentation and actual behavior differ 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='CA+a_5chfsZPkFu=vZDUd+x_Jn_CJPq5LL_Ly5s-VVMgiRdio6Q@mail.gmail.com' \
--to=isaac.b.lewis@gmail.com \
--cc=26955@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).