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 a
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
| 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 f
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
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
Simon Marlow wrote (snipped):
Could you elaborate on the template haskell problem you mentioned? I
don't think template haskell is affected by this (i.e. it's still just
batch linking that requires the -package options, template haskell
should still work just fine without them).
The problem is tha
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 -pac
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, becaus
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
>>
>> En
> > 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
On 07 September 2004 02:21, Dean Herington wrote:
> At 1:52 PM +0100 9/6/04, Simon Marlow wrote:
>> On 06 September 2004 13:43, Simon Peyton-Jones wrote:
>>
>>> * The link step needs -package flags, because it only gets .o
>>> files, and we didn't want it to start hunting through .hi files
>>>
11 matches
Mail list logo
