Haskell98 undefinedness

[Sigbjorn Finne]

So, it's not considered an error if you do something
like

  module A ( B(C), ...some other stuff..., B(D) ) where 
  ...
  data B = C | D 

but C and D is exported. Is the extra flexibility of
allowing duplicates really worth it?

--sigbjorn

----- Original Message ----- 
From: "Simon Peyton-Jones" <simonpj@microsoft.com>
To: "Sigbjorn Finne" <sof@galconn.com>; <haskell@haskell.org>
Sent: Wednesday, September 12, 2001 00:59
Subject: RE: Haskell98 undefinedness


> Yes, it's the same as exporting just B(..) or B(C).
> I guess I should try to make this clearer.
> 
> S
> 
> | -----Original Message-----
> | From: Sigbjorn Finne [mailto:sof@galconn.com] 
> | Sent: 11 September 2001 20:31
> | To: haskell@haskell.org
> | Subject: Haskell98 undefinedness
> | 
> | 
> | What's the meaning of 
> | 
> | module A (B, B(..)) where { data B = C };
> | 
> | Is or isn't C exported? i.e., the H98 report is silent
> | about what it means to have entity duplicates in
> | an export list, possibly with different 'visibility'
> | modifiers.
> | 
> | --sigbjorn
> | 
> | 
> | 
> | _______________________________________________
> | Haskell mailing list
> | Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
> |