From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: Mark H Weaver <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: Let's fix how warnings are specified
Date: Wed, 16 Jan 2013 11:34:43 +0100 [thread overview]
Message-ID: <874nihju0s.fsf@pobox.com> (raw)
In-Reply-To: <87ipj65v9c.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 16 Feb 2012 22:22:07 +0100")
Hi!
Mark, are you still interested in implementing this? It would be very
nice :)
On Thu 16 Feb 2012 22:22, ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Mark H Weaver <mhw@netris.org> skribis:
>>>
>>>> Here's a preliminary proposal:
>>>>
>>>> * Add new pseudo-warning types 'all' and 'default'.
>>>
>>> Yes, but only at the UI level–i.e., in ‘guild compile’, along with
>>> ‘help’.
>>
>> The fundamental problem with this strategy is that it requires a
>> centralized master list of warning types, which makes it very awkward
>> for users to add their own new warning types that can be explicitly
>> disabled.
>
> It can be centralized and user-extensible, can’t it? For instance,
> (system base message) could export ‘register-warning-type!’.
I agree with Ludo here -- for example in GCC, -Wall doesn't actually
enable all warnings, just more of them. You need to be able to list the
set of enabled warning passes I think. Dunno.
> Andy Wingo <wingo@pobox.com> skribis:
>
>> 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.
>
> Yes, sounds good!
This would also be nice :)
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-01-16 10:34 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
2012-02-16 21:22 ` Ludovic Courtès
2013-01-16 10:34 ` Andy Wingo [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=874nihju0s.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).