From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: and-let*, pretty-print unused vars
Date: Sat, 10 Jul 2004 09:41:40 +1000 [thread overview]
Message-ID: <87hdsgkatn.fsf@zip.com.au> (raw)
In-Reply-To: <87n02b67q4.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Wed, 07 Jul 2004 12:35:31 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
>
> I think these would also be fine for 1.6, if you like.
Oh, no, it's not really a bug fix if it has no visible effect :).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-07-09 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 23:49 and-let*, pretty-print unused vars Kevin Ryde
2004-07-07 17:35 ` Rob Browning
2004-07-09 23:41 ` Kevin Ryde [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=87hdsgkatn.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).