Re: Haskell 98 Report: October release
Simon Peyton-Jones wrote: Feedback please... One typo: In the change for Page 93, Appendix A, Standard Prelude the comment should not talk about a fixtity declaration. ^ Bye Christian Sievers ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
Haskell 98 Report: October release
It's that time of the month! Another iteration of the Revised Haskell 98 Report! http://research.microsoft.com/~simonpj/haskell98-revised I'm happy to say that my orbit is diminishing in radius and I shall shortly turn into a black hole. Seriously, the main things I've done this time (apart from a few more typos) is to * revise yet again the wording about export lists * revoke the change that removed Ord as a superclass of Ix But there are other minor things: grep for Oct 2001 in the list of chages. Feedback please... Simon ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
Re: Haskell 98 Report: October release
the main things I've done this time is to * revise yet again the wording about export lists Two of the changes to Export Decls (Section 5.2) now conflict with each other. [Oct 2001] The form `module M' abbreviates the set of all entities whose unqualified name, e, is in scope, and for which the qualified name M.e is also in scope and refers to the same entity as e. [Sept 2001] For example module A ( module B, C.f, g ) where -- an invalid module import qualified B(f,g) import qualified C(f) g = True There are name clashes in the export list between B.f and C.f and between g and B.g even though there are no name clashes within module A. The latter example is now in fact a perfectly valid module, since there is no unqualified entity f in scope, and g and B.g do not refer to the same entity. Regards, Malcolm ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell
Re: Haskell 98 Report: October release
hello, this was a bug in the report, the B import should not be qualified. it has been fixed in the latest version of the report. [Sept 2001] For example module A ( module B, C.f, g ) where -- an invalid module import qualified B(f,g) import qualified C(f) g = True There are name clashes in the export list between B.f and C.f and between g and B.g even though there are no name clashes within module A. The latter example is now in fact a perfectly valid module, since there is no unqualified entity f in scope, and g and B.g do not refer to the same entity. bye iavor -- == | Iavor S. Diatchki, Ph.D. student | | Department of Computer Science and Engineering | | School of OGI at OHSU | | http://www.cse.ogi.edu/~diatchki | == ___ Haskell mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell