> > 2. It would be nice if a parse error when reading ghc-pkg yielded some
> >    information as to the location of the error.
> 
> It should do that... can you give an example?

Here's a simple one (I'm guessing the problem is empty fields - I
thought they were legal because ghc-pkg describe yields them in its
output).

ged:/home/kw217# cat foo.pkg 
name: foo
version:
copyright:
ged:/home/kw217# ghc-pkg-6.3.20041124 register foo.pkg 
Reading package info from "foo.pkg"ghc-pkg: parse error in package
info
ged:/home/kw217# 

--KW 8-)
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to