> More puzzling is that the files that Cabal runs through ghc's CPP
> don't get the # n lines, so we end up with something like this:
(Answering my own message)
Having done some more testing with ghc-6.8.1 and ghc-6.6.1 and cabal's
1.1.6.2 and 1.3, I've realised that the cpp optP-P option in Caba
Alex Jacobson wrote:
My original point (refined) was that I'd like a file extension (.ehs)
that defaults to including all extensions that don't change the meaning
of a .hs program but that may cause a small subset of them not to
compile (e.g. ones that use forall as a type variable, foreign as
My original point (refined) was that I'd like a file extension (.ehs)
that defaults to including all extensions that don't change the meaning
of a .hs program but that may cause a small subset of them not to
compile (e.g. ones that use forall as a type variable, foreign as a
function, or 'd' as
1) is there a single place/wiki/ticket that collects all the
deficiencies of ghci, compared to ghc? things like:
a) which platforms have ghc, but not ghci
b) which features are available in ghc, but not in ghci
c) does ghci encounter bugs where ghc would succeed
d) which of these
I see, all you're saying is you'd like the default to be different.
(That's not the same as saying "Extensions that change syntax are
effectively declared by the use of that syntax", which is what you said
earlier, BTW.)
Well, we could change the default. I don't think it's a great idea
per
I'm doing some testing with GHC 6.6.1 and Cabal 1.3, and I'm trying to
figure out what happens with CPP and Cabal's unlit.
I start with file Test.lhs:
> {-# OPTIONS -fglasgow-exts #-}
> module Test where
> main = putStrLn "hello CPP"
and run command:
ghc -E -x hs -cpp Test.lhs -o Test2.lhs
wh
pepe wrote:
So what's the verdict w.r.t. unlifted things bound by the debugger?
Right now it's quite easy, for example:
Prelude> :m +Data.IORef
Prelude Data.IORef> p <- newIORef False
Prelude Data.IORef> :p p
p = GHC.IOBase.IORef (GHC.STRef.STRef (_t1::GHC.Prim.MutVar#
GHC.Prim.RealWorld Bool)
So what's the verdict w.r.t. unlifted things bound by the debugger?
Right now it's quite easy, for example:
Prelude> :m +Data.IORef
Prelude Data.IORef> p <- newIORef False
Prelude Data.IORef> :p p
p = GHC.IOBase.IORef (GHC.STRef.STRef (_t1::GHC.Prim.MutVar#
GHC.Prim.RealWorld Bool))
Prelude D
Am Dienstag, 27. November 2007 19:21 schrieb Alex Jacobson:
> Simon, I think we've been trying to be too clever...
>
> The simple question is: for a given extension, what is the risk of
> leaving it turned on by default?
The risk is that one thinks that one’s program is Haskell-98-compliant while
