<br><div class="gmail_quote">On Wed, Apr 21, 2010 at 8:41 PM, Stefan Monnier <span dir="ltr"><<a href="mailto:monnier@iro.umontreal.ca">monnier@iro.umontreal.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> Sure, it may make the development version more difficult to build and<br>
> use for non-developers, but then I think that non-developers probably<br>
> shouldn't try to use the development version to begin with.<br>
<br>
</div>That would tend to put off developers.<br>
I would also be interested to hear a concrete response to the OP's<br>
question: which features justify that Agda only works with the very<br>
latest version of every other library it links to (or at least, so it<br>
seems). As a naive outsider, I'd expect that a tool like Agda would<br>
compile just fine with 2-year old tools (tho maybe less efficiently).<font color="#888888"><br></font></blockquote><div><br></div><div>The concrete answer is what Darin said:</div><div><br></div><div>On Tue, Apr 20, 2010 at 12:30 PM, Darin Morrison <span dir="ltr"><<a href="mailto:darinmorrison@gmail.com">darinmorrison@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<div class="im"><br></div>The Cabal support for Agda that I have been working on essentially requires the latest version.</blockquote></div><div><br></div><div>In general we try to keep Agda compatible with the two most recent ghc releases, but in this</div>
<div>case the changes between ghc-6.10 and ghc-6.12 (or the corresponding Cabal releases) were</div><div>too big to make the effort worthwhile.</div><div><br></div><div>/ Ulf</div></div>