parsec3 vs parsec-3.x

Roman Cheplyaka roma at
Mon Jan 31 22:28:01 CET 2011

* Christian Maeder <Christian.Maeder at> [2011-01-31 09:34:47+0100]
> > Perhaps I missed something. Can someone please explain why do we have to
> > have two different third parsecs? Should one of them be deprecated? When
> > would a user prefer one to another?
> parsec-2 (and possibly its compatibility layer) may be deprecated or
> superseded at some stage.
> > I read the description of parsec3 package on hackage, it tries to give
> > some explanation, but still:
> > 
> > 1. It's not clear why "you may want to develop your code using this
> >    subset of parsec3 modules". What advantage does it give?
> The parsec3 package only ensures that you are not using the
> compatibility layer for parsec2 given by the modules
> Text.ParserCombinators.Parsec*, because parsec3 code developed with
> these modules might not work with parsec2 or parsec-2.x.

More information about the Libraries mailing list