There seems to me that when ghci fails to load a file it sometimes
fails to close it. The problem seems to be when there is a parse
error in the file.
My setup:
Windows XP running cygwin
ghc version 6.2.1
Entirely possible. What are the symptoms? Is there an easy way to
On 07 September 2004 11:00, Josef Svenningsson wrote:
There seems to me that when ghci fails to load a file it sometimes
fails to close it. The problem seems to be when there is a parse
error in the file.
My setup:
Windows XP running cygwin
ghc version 6.2.1
Entirely possible. What
Simon Peyton-Jones wrote:
It's documented behaviour.
* import Text.ParserCombinators.Parsec will work without any -package
flags, if any installed package has a module
Text.ParserCombinators.Parsec. It's very tiresome adding -package flags
all the time.
* The link step needs -package flags,
On 07 September 2004 12:24, George Russell wrote:
Simon Peyton-Jones wrote:
It's documented behaviour.
* import Text.ParserCombinators.Parsec will work without any -package
flags, if any installed package has a module
Text.ParserCombinators.Parsec. It's very tiresome adding -package
On 07 September 2004 16:45, George Russell wrote:
The problem is that if package A includes an import of
Text.ParserCombinators.Parsec and package B includes a module
which uses Template Haskell code that requires package B,
you are liable to get things falling over at compile-time.
This has
SimonM:
So you're proposing that -package options should *always* be required?
Why is it necessary to provide -package options at all?
ghc-pkg knows about all the packages in your system so it could just
implicitly add -package $x for every package when compiling or linking.
When would you
| Why is it necessary to provide -package options at all?
|
| ghc-pkg knows about all the packages in your system so it could just
| implicitly add -package $x for every package when compiling or
linking.
That's exactly what I think. Currently we require the -package flags
when linking solely
On Tuesday 07 September 2004 17:52, Simon Peyton-Jones wrote:
That's exactly what I think. Currently we require the -package flags
when linking solely for efficiency reasons: linking would be slow if ld
was given every lib.a file installed for that compiler. But perhaps
that should be the
Alastair Reid wrote (snipped):
Why is it necessary to provide -package options at all?
ghc-pkg knows about all the packages in your system so it could just
implicitly add -package $x for every package when compiling or linking.
My current need at least is to disable the lang, text, data packages
