<html>#2089: piraha uses Carp::confess() rather than CST_error
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>assignee:</td><td>Steven R. Brandt (was )</td></tr>
<tr><td>responsible:</td><td>[] (was )</td></tr>
</table></p>
<p>It really shouldn't. Instead it should use the CST provided CST_error function and continue parsing. Right now it stops at the first parsing error.</p>
<p>I think this has been a point of contention of mine before and I do understand that recovering from a parse error is hard (and is why eg gcc does no longer use a auto-generated parser but instead a hand-written one apparently). However failing after the first parsing error is really annoying. At least it should continue with the next ccl file.</p>
<p><strong>Keyword:</strong> piraha</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2089/piraha-uses-carp-confess-rather-than'>https://bitbucket.org/einsteintoolkit/tickets/issues/2089/piraha-uses-carp-confess-rather-than</a></p>
</html>