On Wed, 2008-08-27 at 16:43 +0100, Simon Peyton-Jones wrote: > | The documentation should also appear in: > | > | > http://hackage.haskell.org/packages/archive/Cabal/1.4.0.1/doc/html/Language-Haskell-Extension.html > | > | It might be easier if the information was duplicated there, as then it > | would be hoogle-able (although making the GHC manual hoogle-able is on > | the Hoogle bug list > > I don't know how it gets there... GHC might have more extensions than > Cabal for example? Anyway, I'm perhaps-selfishly sticking to getting > the GHC user manual right.
As I understood it, the intention was that this enumeration is supposed to be a central shared registry of language extensions. So all the ghc extensions should be there. We expect implementers to add new extensions to this list when they believe the extensions are ready for public consumption. Unknown/local/experimental extensions can be used in .cabal files and they will work if ghc supports them (though one gets a warning) but packages using unknown/unregistered extensions cannot be uploaded to hackage. Since we do refer people to the haddock docs for this Extension enumeration I thought it'd be nice to have it documented in the same place. I've filed a task for some volunteer: http://hackage.haskell.org/trac/hackage/ticket/344 Duncan _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
