unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 11988-done@debbugs.gnu.org, Daniel Llorens <daniel.llorens@bluewin.ch>
Subject: bug#11988: eval-case redefinition?
Date: Tue, 21 Jan 2014 00:26:54 -0500	[thread overview]
Message-ID: <87vbxdoqg1.fsf@netris.org> (raw)
In-Reply-To: <87r4pb5m64.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 06 Oct 2012 23:24:19 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Daniel Llorens <daniel.llorens@bluewin.ch> skribis:
>
>> I was cleaning up an old script which goes like this:
>>
>> (define (eval-case ...)  ...  val)
>>
>> (define var (eval-case ...))
>>
>> This worked from the REPL, but when loading the file with (load
>> "script"), var was always #<unspecified>. It turns out that (my)
>> eval-case is never executed in this case.
>
> It turns out that ‘eval-case’ is a macro, and it gets macro-expanded in
> the RHS of ‘define var’ above.

This bug is now fixed on the stable-2.0 branch.

  http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=8de355d08e25a877326489c4b0eb09d313c548dc

I'm closing the bug now.  Feel free to reopen if you think there's still
a problem.

    Thanks!
      Mark





  reply	other threads:[~2014-01-21  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 13:22 bug#11988: eval-case redefinition? Daniel Llorens
2012-10-06 21:24 ` Ludovic Courtès
2014-01-21  5:26   ` Mark H Weaver [this message]
2013-03-05 16:15 ` Andy Wingo

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=87vbxdoqg1.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=11988-done@debbugs.gnu.org \
    --cc=daniel.llorens@bluewin.ch \
    --cc=ludo@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).