+1. Thanks for doing this. I ended up branching Parsec2 locally at work. I'll offer more patches if I find any bugs, but besides that one little one that kicked off this thread, Parsec2 has been rock solid.<div><br>
</div><div>-Greg</div><div> </div><div><br><div class="gmail_quote">On Wed, Jun 9, 2010 at 8:41 PM, Antoine Latter <span dir="ltr"><<a href="mailto:aslatter@gmail.com">aslatter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Sat, Apr 3, 2010 at 6:21 AM, wren ng thornton<br>
<<a href="mailto:wren@community.haskell.org">wren@community.haskell.org</a>> wrote:<br>
><br>
> I'd argue that it's acceptable, at least under this plan:<br>
><br>
> * fork parsec-2.1 as parsec2-2.1<br>
> * continue to develop parsec2-* (as desired)<br>
> * deprecate parsec<3 with message to switch to parsec2-*<br>
> * continue parsec>=3 as parsec-*<br>
><br>
><br>
> The harm is minimal because:<br>
><br>
> (a) anyone who is too lazy to upgrade their .cabal can still use parsec-2.1<br>
> until it bitrots<br>
><br>
> (b) anyone who is too lazy to upgrade their code to parsec>=3 can just<br>
> update their .cabal to use parsec2-* if they want to avoid bitrot<br>
><br>
> (c) anyone using parsec>=3 won't notice a thing.<br>
><br>
<br>
I really like this plan, so I've finally gotten something done in this<br>
direction.<br>
<br>
I pulled parsec-2.1.0.1 off of hackage and stuffed it into a fresh<br>
darcs repo, and I've made two branches off of it:<br>
<br>
<a href="http://community.haskell.org/~aslatter/code/parsec-2/parsec2/" target="_blank">http://community.haskell.org/~aslatter/code/parsec-2/parsec2/</a><br>
<br>
This is a new package that I am willing to maintain. I expect to be<br>
limiting my actions to maintaing compatibility with as many GHC<br>
releases as practical, and I will accept patches needed to get working<br>
on other implementations. Fixes such as Greg's above are also<br>
appropriate when kept in sync with main-line.<br>
<br>
<br>
<a href="http://community.haskell.org/~aslatter/code/parsec-2/parsec-deprecated/" target="_blank">http://community.haskell.org/~aslatter/code/parsec-2/parsec-deprecated/</a><br>
<br>
I propose to upload this to hackage as parsec-2.1.0.2. It is identical<br>
in all respects to 2.1.0.1, except each module is marked as<br>
deprecated, producing the following warning:<br>
<br>
<br>
Text/ParserCombinators/Parsec/Language.hs:27:0:<br>
Warning: In the use of type constructor or class `LanguageDef'<br>
(imported from Text.ParserCombinators.Parsec.Token):<br>
Deprecated: "Please use the parsec2 package or upgrade to<br>
a higher version of parsec"<br>
<br>
Any comments on either of these two branches? Is parsec2 the right<br>
name for the branch package? Does anyone want to see anything<br>
different in the package description text?<br>
<br>
Is the next step getting parsec2 into the Platform, and updating<br>
inter-platform deps?<br>
<br>
Take care,<br>
<font color="#888888">Antoine<br>
</font></blockquote></div><br></div>