Ashley Yakeley wrote:
Any word on whether this has been/will be fixed? [...]
Well, it's fixed in CVS for quite a while, but it's up to Simon^2 when a
new GHC release comes out.
Personally I'd favour tossing this "feature" altogether, [...]
Me too... :-P * * *
Cheers,
S.
___
Last month I wrote:
> The 6.2 version of ghc-pkg is incorrectly parses commas within quotes.
> Here's a simple example:
>
> $ echo 'Package {name="ptest",extra_ld_opts=["a,b,c"]}' | sudo ghc-pkg -a
> $ ghc-pkg -s ptest
> Package
>{name = "ptest",
> auto = False,
> import_dirs = [],
>
Ashley Yakeley wrote:
Might it not be better to do it this way?
deps = base,haskell98,network
[${deps},"foo"] => (expand $-reference)
[base,haskell98,network,"foo"] => (quote things)
["base","haskell98","network","foo"]
The idea is that unquoted things get implicitly quoted, so you don't
In article <[EMAIL PROTECTED]>,
Sven Panne <[EMAIL PROTECTED]> wrote:
> which is plainly wrong. Now we do this *only* when a variable occurs on its
> own,
> like:
>
> ["${deps}","foo"] => ["base","haskell98","network","foo"]
>
> I have slight doubts about this obscure feature, but Sigbjorn
Ashley Yakeley wrote:
The 6.2 version of ghc-pkg is incorrectly parses commas within quotes. [...]
This was a side-effect of a slighty obscure feature of ghc-pkg. I've made
things more robust now. From the CVS log:
--
Fixe
The 6.2 version of ghc-pkg is incorrectly parses commas within quotes.
Here's a simple example:
$ echo 'Package {name="ptest",extra_ld_opts=["a,b,c"]}' | sudo ghc-pkg -a
$ ghc-pkg -s ptest
Package
{name = "ptest",
auto = False,
import_dirs = [],
source_dirs = [],
library_dirs =
