RE: ghc warnings messed up in 6.01

2003-12-16 Thread Simon Peyton-Jones
Done, I believe. It'll be in the next release (6.3/6.4). Simon | -Original Message- | From: [EMAIL PROTECTED] [mailto:glasgow-haskell-users- | [EMAIL PROTECTED] On Behalf Of Mike Gunter | Sent: 07 December 2003 16:50 | To: [EMAIL PROTECTED] | Subject: Re: ghc warnings messed up in

RE: ghc warnings messed up in 6.01

2003-12-08 Thread Simon Marlow
> Simon seems to have agreed that The Right Thing is to treat bindings > with names beginning with an underscore as if they are used w.r.t. to > the bindings they use (they're already treated as used w.r.t. warnings > for themselves.) With this enhancement (and the other warning fixes > apparent

Re: ghc warnings messed up in 6.01

2003-12-07 Thread Mike Gunter
Simon seems to have agreed that The Right Thing is to treat bindings with names beginning with an underscore as if they are used w.r.t. to the bindings they use (they're already treated as used w.r.t. warnings for themselves.) With this enhancement (and the other warning fixes apparently already

Re: ghc warnings messed up in 6.01

2003-12-07 Thread Sven Panne
John Meacham wrote: [...] ;ghc -W -fglasgow-exts Foo.hs The current HEAD version (no idea about the release branch) of ghc correctly says: Foo.hs:1: Warning: Module `List' is imported, but nothing from it is used (except perhaps instances visible in `List') Foo.hs:7: Warning: Defi

ghc warnings messed up in 6.01

2003-12-07 Thread John Meacham
has anyone else noticed that the warnings generated by ghc appear to have become quite incorrect in many cases? in particular, the 'defined but not used' warning is generated spuriously a lot. almost as if it is being checked after dead code elimination and desugaring of some sort.. here is an ex