Re: import prefers module in package over local module

2006-05-04 Thread Simon Marlow
Michael Marte wrote: Simon Marlow wrote: Deprecation warnings seem to be working fine: $ ghc -c Foo.hs -package text Foo.hs:2:0: Warning: Module `Pretty' is deprecated: This module has moved to Text.PrettyPrint.HughesPJ Also, the documentation for the text package clearly

Re: import prefers module in package over local module

2006-05-04 Thread Michael Marte
Simon Marlow wrote: Deprecation warnings seem to be working fine: $ ghc -c Foo.hs -package text Foo.hs:2:0: Warning: Module `Pretty' is deprecated: This module has moved to Text.PrettyPrint.HughesPJ Also, the documentation for the text package clearly states in several plac

RE: import prefers module in package over local module

2006-05-03 Thread Simon Marlow
On 03 May 2006 13:27, Michael Marte wrote: > Simon Marlow wrote: > >> Tomasz Zielonka wrote: >> >>> On Wed, May 03, 2006 at 11:53:19AM +0100, Simon Marlow wrote: >>> I'm afraid I don't understand: there's no Pretty module in the standard libraries, only Text.PrettyPrint. >>> >>> >>>

Re: import prefers module in package over local module

2006-05-03 Thread Michael Marte
Simon Marlow wrote: Tomasz Zielonka wrote: On Wed, May 03, 2006 at 11:53:19AM +0100, Simon Marlow wrote: I'm afraid I don't understand: there's no Pretty module in the standard libraries, only Text.PrettyPrint. There is a Pretty module in the text package. It seems that Michael uses "ghc

Re: import prefers module in package over local module

2006-05-03 Thread Simon Marlow
Tomasz Zielonka wrote: On Wed, May 03, 2006 at 11:53:19AM +0100, Simon Marlow wrote: I'm afraid I don't understand: there's no Pretty module in the standard libraries, only Text.PrettyPrint. There is a Pretty module in the text package. It seems that Michael uses "ghc -package text". Ok (t

Re: import prefers module in package over local module

2006-05-03 Thread Tomasz Zielonka
On Wed, May 03, 2006 at 11:53:19AM +0100, Simon Marlow wrote: > I'm afraid I don't understand: there's no Pretty module in the standard > libraries, only Text.PrettyPrint. There is a Pretty module in the text package. It seems that Michael uses "ghc -package text". Best regards Tomasz __

Re: import prefers module in package over local module

2006-05-03 Thread Simon Marlow
I'm afraid I don't understand: there's no Pretty module in the standard libraries, only Text.PrettyPrint. Could you describe in more detail what's going wrong? (provide example code and exact command lines, cut & paste error messages). Cheers, Simon Michael Marte wrote: Simon, I c

Re: import prefers module in package over local module

2006-05-02 Thread Michael Marte
Simon, I checked the version of ghc I use: It's 6.4.1. Michael Simon Marlow wrote: Michael Marte wrote: I am migrating a project from ghc 6.2 to ghc 6.4. This project has a module called Pretty and that's where my problems start. When importing Pretty, ghc does not consider my local defini

Re: import prefers module in package over local module

2006-05-02 Thread Simon Marlow
Michael Marte wrote: I am migrating a project from ghc 6.2 to ghc 6.4. This project has a module called Pretty and that's where my problems start. When importing Pretty, ghc does not consider my local definition but the Pretty module from the standard library (which is an alias for Text.Prett

import prefers module in package over local module

2006-05-02 Thread Michael Marte
Hello *, I am migrating a project from ghc 6.2 to ghc 6.4. This project has a module called Pretty and that's where my problems start. When importing Pretty, ghc does not consider my local definition but the Pretty module from the standard library (which is an alias for Text.PrettyPrint.Hughe