Subject: bug#26955: closed (macroexpand: documentation and actual behavior differ)

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 16 May 2021 18:06:02 +0000

Your bug report

#26955: macroexpand: documentation and actual behavior differ

which was filed against the guile package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
26955: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26955
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: macroexpand: documentation and actual behavior differ
From: Taylan Kammer <[email-masked]>
To: [email-masked]
Date: Sun, 16 May 2021 20:05:49 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Closing this report as it seems fixed.

-- 
Taylan

Subject: macroexpand: documentation and actual behavior differ
From: isaac lewis <[email-masked]>
To: [email-masked]
Date: Tue, 16 May 2017 04:48:12 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

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