<div class="markdown_content"><ul>
<li><strong>status</strong>: open --> closed-wont-fix</li>
<li><strong>Comment</strong>:</li>
</ul>
<p>In the 8 years since we last commented on this issue, we have radically changed our ideas on what CWB v 4 will do. One of the things it WON'T do is use the present CQP code for error returns (or, in fact, much of anything). Stable CWB 3.5 will retain the complained-of behaviour for compatibility; all new utilities/applications for v4 will be built from the ground up to return error codes on exit in a <em>sane</em> way.</p>
<hr/>
<p><strong> <a class="alink strikethrough" href="https://sourceforge.net/p/cwb/bugs/9/">[bugs:#9]</a> Inconsistency in CQP exit codes</strong></p>
<p><strong>Status:</strong> closed-wont-fix<br/>
<strong>Group:</strong> TODO-4.0<br/>
<strong>Labels:</strong> CQP engine <br/>
<strong>Created:</strong> Thu Mar 22, 2007 09:40 AM UTC by Peter Adolphs<br/>
<strong>Last Updated:</strong> Fri Feb 10, 2012 03:51 AM UTC<br/>
<strong>Owner:</strong> Stefan Evert</p>
<p>cqpcl always returns 0 as the exit code, also if an error occured. In case of error, it should return a non-zero exit code instead.</p>
<hr/>
<p>Sent from sourceforge.net because cwb@sslmit.unibo.it is subscribed to <a href="https://sourceforge.net/p/cwb/bugs/">https://sourceforge.net/p/cwb/bugs/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/cwb/admin/bugs/options.">https://sourceforge.net/p/cwb/admin/bugs/options.</a> Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>