Bug in Parsec.Token

[Ganesh Sittampalam]

On Mon, 15 Mar 2010, Don Stewart wrote:

> Parsec98 is kind of a cool name, actually.

The parsec98 name sounds cool, but if used, it'll last a long time I think 
it'll just be sowing more confusion for a future in which the origins of 
the name have faded into obscurity. And what if someone wants to keep it 
roughly as is, but bring it up to date with the latest Haskell standard? 
The name would be rather a barrier then.

If versions are going to be forked off, let's aim for a consistent naming 
scheme - parsec2, QuickCheck1, etc. Not sure how to deal with HaXml 1.13 
(the other strong candidate for this kind of treatment).

Ganesh