Re: [cc65] Calling another program: exec() ?

Hi,

>> It may be possible to return on some errors, so
>> I think the error code is still a good idea and not too much overhead.

> Yup. :-)

Maybe there's a misunderstanding (?). It makes certainly sense to be
able to inform the caller about errors. The only thing I'm saying is
that there's no need for exec() to have a return value as the return
value will *ALWAYS* be -1. If exec() returns to the caller than it is
already evident that there was an error. When exec() returns the
caller can directly go ahead and check errno. Again, technically
there's no point in a return value that is a constant - is it?

Regards,
Oliver
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.