<br><br><div class="gmail_quote">On Sun, Jun 12, 2011 at 7:12 PM, Antoine Latter <span dir="ltr"><<a href="mailto:aslatter@gmail.com" target="_blank">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">
<div><div></div><div>Types from differing versions of the same module are specifically not</div></div>
compatible - even if they are defined identically (in this case they<br>
are different, though).<br>
<br>
You can do one of two things:<br>
<br>
1. Edit the package description of the package that wants the older<br>
version of parsec to allow to use the new one. Also, it helps to<br>
slightly bump the version number of the package when you do this.<br>
<br>
2. Use the older version of parsec in your software. You already have<br>
it installed (or else the package you want to use wouldn't be able to<br>
load!). If you're using ghci you can start it with the option<br>
'-package parsec-2.1.0.1'.<br></blockquote><div><br></div><div>I understand that types from different versions of a module are incompatible. What I don't understand is why one module is using a new version of Parsec when it is constrained to use the "old" one (I control both modules. Their package descriptions contain the same line). Is this a cabal-dev bug? </div>
<div><br></div></div><div>I'll try the "-package parsec-2.1.0.1" tip, but this is /not/ a long term solution to my problem.</div>