>Sounds good. Since we're redesigning this, maybe a more extensible way
>can be preferable?
>
>(just a mockup)
>
>typedef enum tcstatus_ TCStatus;
>enum tcstatus_
> TC_ERROR = -1, /* unrecoverable error */
> TC_OK = 0, /* all fine */
> TC_RETRY, /* generic recoverable error */
> /* add more recoverable errors here */
>};
I don't know that we need to make things too complicated, though it
probably couldn't hurt to go over the set of returns we expect to see.
I'm personally still partial to the idea of returning a simple boolean
value to indicate success or failure, and (for functions that need it)
return a detailed status code in a separate pass-by-reference parameter.
>Another issue:
>should we limit to module operations return code or should we
>make things more generic?
Right now I think we only need to worry about module interface
functions--local stuff can do whatever it wants, and the main code doesn't
need to worry about it.
And now I need to get to sleep before the sun comes up again ;)
--Andrew Church
[EMAIL PROTECTED]
http://achurch.org/
