On Thu, Aug 28, 2008 at 10:59:53AM +0100, Simon Marlow wrote:
>
> Nevertheless we should move towards specifying everything about a flag in
> one place. I think Ian had some thoughts along those lines?
Right, we have a ticket for that:
http://hackage.haskell.org/trac/ghc/ticket/1880
Some of
Claus Reinke [mailto:[EMAIL PROTECTED]
| Sent: 28 August 2008 12:28
| To: Simon Peyton-Jones; Ian Lynagh; Simon Marlow
| Cc: cvs-ghc@haskell.org
| Subject: Re: Docs for language flags
|
| | This is the first time I've looked at (b), so I don't mind it going,
| | but the syntax info deserves
| This is the first time I've looked at (b), so I don't mind it going,
| but the syntax info deserves its own section, to be easy to find
| without blowing up the flag reference section.
Interesting. Any suggestions about where would be "easy to find"?
Or what the section would look like. Woul
Simon Peyton-Jones wrote:
Ian, Simon
The documentation for language extensions appears in GHC's user manual in
*three* places:
(a) The flag summary
http://www.haskell.org/ghc/docs/latest/html/users_guide/flag-reference.html#id352860
(b) A section at the beginning of Chapter 8:
http://www.ha
| This is the first time I've looked at (b), so I don't mind it going,
| but the syntax info deserves its own section, to be easy to find
| without blowing up the flag reference section.
Interesting. Any suggestions about where would be "easy to find"? Or what the
section would look like. Would
This is the first time I've looked at (b), so I don't mind it going,
but the syntax info deserves its own section, to be easy to find
without blowing up the flag reference section.
I just wanted to throw in a reference to
http://hackage.haskell.org/trac/ghc/ticket/1880
Unify flag descrip
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
> |
> | 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-selfi
| 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
| th
Hi
> The documentation for language extensions appears in GHC's user manual in
> *three* places:
>
> (a) The flag summary
> http://www.haskell.org/ghc/docs/latest/html/users_guide/flag-reference.html#id352860
>
> (b) A section at the beginning of Chapter 8:
> http://www.haskell.org/ghc/docs/lat
Ian, Simon
The documentation for language extensions appears in GHC's user manual in
*three* places:
(a) The flag summary
http://www.haskell.org/ghc/docs/latest/html/users_guide/flag-reference.html#id352860
(b) A section at the beginning of Chapter 8:
http://www.haskell.org/ghc/docs/latest/ht
11 matches
Mail list logo
