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

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

Trouble using (current-filename)

2012-02-14 Thread Mark H Weaver
I put the following test module in my load path: (define-module (current-filename-fail) :export (my-filename)) (define my-filename (current-filename)) (define (force-a-warning-message) (identity 1 2 3)) And this is what I see with Guile 2.0.5: GNU Guile 2.0.5 Copyright (C) 1995-201