Re: Let's fix how warnings are specified

2013-01-16 Thread Andy Wingo
Hi! Mark, are you still interested in implementing this? It would be very nice :) On Thu 16 Feb 2012 22:22, l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Mark H Weaver skribis: >>> Here's a preliminary proposal: >>

Re: Let's fix how warnings are specified

2012-02-16 Thread Ludovic Courtès
Hello! Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver 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 fundam

Re: Let's fix how warnings are specified

2012-02-15 Thread Andy Wingo
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 writes: > (compile x #:opts '(#:warnings (default no-format no-bad-case-datum))) Let's pave this cowpath and add a #:warnings o

Re: Let's fix how warnings are specified

2012-02-14 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver 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 req

Re: Let's fix how warnings are specified

2012-02-14 Thread Ludovic Courtès
Hi Mark, Mark H Weaver 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’. At the programming level there are better ways to do this, namely (map car %warning-types) and %au