Bug in Parsec.Token

[Isaac Dupree]

On 04/01/10 23:39, Greg Fitzgerald wrote:
> It sounds to me like forking Parsec 3 would cause quite a bit of pain
> for other packages on Hackage, but forking Parsec 2.1 to Parsec98
> would be relatively painless.

I like the idea of parsec98... But wouldn't then, the .cabal file of 
*every* package that wished to depend on the Platform and its parsec, 
(a.k.a. parsec98), have to be changed?

-Isaac