Thanks .. very interesting on the cabal "parsers". I somehow got around my problem ... forgot how though.<br><br>Vasili<br><br><div class="gmail_quote">On Sat, May 9, 2009 at 10:48 AM, Duncan Coutts <span dir="ltr"><<a href="mailto:duncan.coutts@worc.ox.ac.uk">duncan.coutts@worc.ox.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Wed, 2009-05-06 at 19:37 -0500, Vasili I. Galchin wrote:<br>
> are them some CLI switches I can enable in order to better determine<br>
> what "parse error" is??<br>
<br>
</div>The problem is that we're using a parser that has no support for<br>
producing parse errors (Text.ParserCombinators.ReadP). The only reason<br>
we're using this parser is because it's the only one in the core<br>
libraries. Packages like parsec cannot be used in Cabal because Cabal is<br>
a core library and parsec is not.<br>
<br>
For this reason we've been considering just copying another parser<br>
module into Cabal so that we can have saner (and quicker) parsing.<br>
<div class="im"><br>
> Kind regards, Vasili<br>
><br>
> On Wed, May 6, 2009 at 6:12 PM, Vasili I. Galchin<br>
> <<a href="mailto:vigalchin@gmail.com">vigalchin@gmail.com</a>> wrote:<br>
> sorrily nope, Brian ...<br>
<br>
</div>For what it's worth, Brian was right, you cannot have a trailing comma<br>
in a list field. Perhaps there was an additional error in the file that<br>
we could not see in the bit you posted.<br>
<font color="#888888"><br>
Duncan<br>
<br>
</font></blockquote></div><br>