From: "Daniel Llorens del Río" <dll@bluewin.ch>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: bug in 1.9.9
Date: Wed, 31 Mar 2010 18:12:43 +0200 [thread overview]
Message-ID: <85C0E10D-8195-4736-8F48-4E3F19A1CB0E@bluewin.ch> (raw)
In-Reply-To: <DC61943E-638A-47F6-B3D3-539D65D6706E@bluewin.ch>
On 31 Mar, 2010, at 17:55, Daniel Llorens del Río wrote:
> Although this one also works…
>
> > (call-with-values (lambda () (f #s32() #f64())) (lambda (a b)
> (format #f "~a ~a" a b)))
> => "#s32() #f64()"
Sorry, this should be … (lambda () (values #s32() #f64())) …
Regards,
Daniel
prev parent reply other threads:[~2010-03-31 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94.9E.26951.FBE797B4@mx15>
2010-03-30 15:02 ` compiler bug in 1.9.9 Daniel Llorens del Río
2010-03-30 19:24 ` Andy Wingo
2010-03-31 15:55 ` Daniel Llorens del Río
2010-03-31 16:12 ` Daniel Llorens del Río [this message]
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=85C0E10D-8195-4736-8F48-4E3F19A1CB0E@bluewin.ch \
--to=dll@bluewin.ch \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.com \
/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).