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.
A reasonable request, but unfortunately it didn't occur to the CWB developer that CQP might want to keep track of its internal error status (except by printing an error message on screen). So there seems to be no easy way for the cqpcl main loop to detect an error condition and signal it to the calling program (except a syntax error in the command parser, which should return an exit code of 1).
Current recommendation: use Perl's interactive CQP interface instead, which catches the CQP error message.
Renamed bug, as cqpcl is depracated and therefore a wont-fix, but the same consideration applies to the main CQP (and cqpserver?).
I have now added in (between v 3.4.3 and 3.4.4) a global error variable that can be used for this purpose; CQP tests this value to determine its exit code. Fro 4.0 we need to make sure the error variable is set at any point where an error happens that does not lead to an immediate abort. see cqp/cqp.c, cqp/cqp.h
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.