From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Let's fix how warnings are specified
Date: Wed, 15 Feb 2012 23:09:46 +0100 [thread overview]
Message-ID: <877gznn3yt.fsf@pobox.com> (raw)
In-Reply-To: <87hayt4alh.fsf@netris.org> (Mark H. Weaver's message of "Tue, 14 Feb 2012 11:56:58 -0500")
Hi,
FWIW, I'm fine with whatever you all agree upon in the end, though I am
sympathetic to Mark's concerns here.
One thing:
On Tue 14 Feb 2012 17:56, Mark H Weaver <mhw@netris.org> writes:
> (compile x #:opts '(#:warnings (default no-format no-bad-case-datum)))
Let's pave this cowpath and add a #:warnings option to compile. It
could default to #f. If it's not #f, then we require it to be a list,
and append `(#:warnings ,warnings) to the #:opts.
IMO anyway :)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-02-15 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 3:57 Let's fix how warnings are specified Mark H Weaver
2012-02-14 14:00 ` Ludovic Courtès
2012-02-14 16:56 ` Mark H Weaver
2012-02-15 22:09 ` Andy Wingo [this message]
2012-02-16 21:22 ` Ludovic Courtès
2013-01-16 10:34 ` 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=877gznn3yt.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.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).