ginal Message-
| From: Thomas Hallgren [mailto:[EMAIL PROTECTED]
| Sent: 18 January 2005 22:12
| To: Simon Peyton-Jones; glasgow-haskell-users@haskell.org
| Cc: [EMAIL PROTECTED]
| Subject: Re: self-import
|
| Simon Peyton-Jones wrote:
|
| >I quite liked this idea until I thought of this:
| >
Simon Peyton-Jones wrote:
I quite liked this idea until I thought of this:
module Doc.Pretty.Long( M.f, f ) where
import qualified M( f )
import Doc.Pretty.Long as M
f x = x
The second import decl imports all the things exported by
Doc.Pretty.Long. But what doe
On Tue, 2005-01-18 at 10:43 +, Simon Peyton-Jones wrote:
> | And if it turns out we are in the mood to look at extending the
> | inport/export/module syntax perhaps we could also consider the
> qualified
> | export idea posted a few weeks ago.
> |
> | That was so that you could say:
> |
> |
| And if it turns out we are in the mood to look at extending the
| inport/export/module syntax perhaps we could also consider the
qualified
| export idea posted a few weeks ago.
|
| That was so that you could say:
|
| import Graphics.UI.Gtk
|
| and then use Button.setText (rather than buttonSet
On Tue, 2005-01-18 at 10:13 +, Simon Peyton-Jones wrote:
> I think what you want is actually more directly stated thus:
>
> module Doc.Pretty.Long( ... ) as M where
> ...
>
> The 'as M' in the module header gives an alias for Doc.Pretty.Long just
> as it does for an import stat
trying to compile is not available. It would be nice if
ghc
| could recognize the self-import case and handle it directly.
I quite liked this idea until I thought of this:
module Doc.Pretty.Long( M.f, f ) where
import qualified M( f )
import Doc.Pretty.Long as M
ile is not available. It would be nice if ghc
could recognize the self-import case and handle it directly.
John
--
John Meacham - ârepetae.netâjohnâ
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailma
