Serge D. Mechveliani wrote:
Who knows, please, where there are explained
hierarchical module names?
Is this a matter of Haskell-98 or of GHC ?
I looked into both of them (and also a bit into [EMAIL PROTECTED])
but could not find a basic explanation of the point, somehow missed.
The
Who knows, please, where there are explained
hierarchical module names?
Is this a matter of Haskell-98 or of GHC ?
I looked into both of them (and also a bit into [EMAIL PROTECTED])
but could not find a basic explanation of the point, somehow missed.
Suppose that my user package called
sed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: allow hierarchical module names with --make
Initial Comment:
It would be convenient (and consistent) to allow the
use of hierarchical module names with --make, so that
something like:
ghc -isource_d
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: allow hierarchical module names with --make
Initial Comment:
It would be convenient (and consistent) to allow the
use of hierarchical module names with --make, so that
somethin
> I use GHC 5.00.2 on Solaris 2.6 at the university and am unable to use
> hierarchical module names --- with and without the
> -fglasgow-exts switch. GHCi
> notifies me of parse errors on the module name. What is
> interesting is that if
> my module with hierarchical nam
Wolfgang Jeltsch <[EMAIL PROTECTED]> writes:
> Aren't hierarchical module names supported yet in GHC
> 5.00.2?
No, not as far as I remember.
> At home with GHC 5.02 under Linux everything works fine.
I believe they are ne
Hello,
I use GHC 5.00.2 on Solaris 2.6 at the university and am unable to use
hierarchical module names --- with and without the -fglasgow-exts switch. GHCi
notifies me of parse errors on the module name. What is interesting is that if
my module with hierarchical name imports a module which
[ thread moved from [EMAIL PROTECTED] to
[EMAIL PROTECTED] ]
> "Simon Marlow" <[EMAIL PROTECTED]> writes:
>
> > You must give the full module name in the header, eg.
>
> > module A.B.C where
>
> This surprised me somewhat, and I must have missed any
> discussion/rationale. Could you elabo
"Simon Marlow" <[EMAIL PROTECTED]> writes:
> You must give the full module name in the header, eg.
> module A.B.C where
This surprised me somewhat, and I must have missed any
discussion/rationale. Could you elaborate/point me at the relevant
information?
It seems to me that A.B could b
> The release notes for ghc 5.02.1 say:
>
>1.4.4. New experimental features
>
> Partial support for hierarchical module names.
>
> - but I could not find a document describing how to use this feature.
>
> Is it possible to use hierarchical module names
The release notes for ghc 5.02.1 say:
1.4.4. New experimental features
Partial support for hierarchical module names.
- but I could not find a document describing how to use this feature.
Is it possible to use hierarchical module names with ghc at present, and if so,
how does one
11 matches
Mail list logo
