Serge D. Mechveliani wrote:
Dear GHC developers,
ghc-6.8.2 compiles {-# SCC ab cd #-} as all right.
And the GHC candidate of May 27, 2008 reports the error:
spaces are not allowed in SCC.
Do you think that this latter has more sense?
Is not this a matter of the programmer to give
Duncan Coutts wrote:
On Fri, 2007-10-19 at 10:54 -0300, Isaac Dupree wrote:
How can user who does not modify Cabal file choose between all three of
-O0, -O and -O2?
They cannot. Cabal currently only support a binary notion of
optimisations. So it's either -O0 or -O.
(Not knowing about
defines, for example, whether to compile the library with -O, with
-O2, or with -Onot.
The meaning of these options is explained in the GHC documentation.
Ok, so you can get rid of -O and -prof and instead use:
runghc Setup.hs configure
with our without the following options:
Serge D. Mechveliani wrote:
People,
here is a more precise report about empty _export_ in
ghc-6.8.1-candidate:
I use
module M1 (f, module M2)
where
import M2 ()
f = ...
in the situation when M1 imports some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Augustsson wrote:
And ghci gives the only sensible answer. Once you start trying to be
clever
you're on the slippery slope to undecidability. How would one know
where to
stop?
I would be most perturbed if Haskell were to try and ignore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Peyton-Jones wrote:
[Redirecting to ghc-bugs]
| module A where
| data A = A { label :: Int }
|
| module B where
| data B = B { label :: Int }
|
| b :: B
| b = B { label = 0 }
|
| x ::
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Mitchell wrote:
http://www.cs.york.ac.uk/fp/haddock/filepath/System-FilePath-Posix.html#v%3AmakeRelative
The two basic QuickCheck properties are:
takeDrive x == x || makeRelative x (x `combine` y) == y
isRelative x || y `combine`
