On Mon, Jun 8, 2009 at 8:19 PM, Bruno Haible <br...@clisp.org> wrote:
> Sam Steingold wrote:
>
>> I urge you to avoid abort in favor of returning an error code and
>> document that aborting on certain errors is the right behavior.
>
> If I did this, the risk that a bug does not get reported would be too
down with the nannies!
let us assume that I threw in the anti-totalitarian-programming
diatribe here. :-)
(I am too lazy to actually do it).
> high. For the average user, abort() is acceptable. (Note the module
> is not suitable for use in libraries.)
then it is not suitable for clisp either.
you could easily make it suitable for libraries too by returning an
exit code from the foo_low function and adding
int foo () {
if (foo_low() == NEED_ABORT) {
fprintf(stderr,"life sucks\n");
abort();
}}
or something.
--
Sam Steingold <http://sds.podval.org>
