On Mon, 09 Oct 2006 04:24:10 JST
[EMAIL PROTECTED] (Andrew Church) wrote:
> >I like to use TC_EXPORT_* macros for return values instead direct integers,
> >but I can happily live with either solution.
> >I'd just like to establish an official line of conduct :)
> Sorry, I didn't realize that was you ;)
Don't worry, it isn't a problem :)
> I though TC_EXPORT_* were
> part of OMS and therefore going away. If we're going to use constants, we
> should probably pick better names. (Maybe just TC_OK and TC_ERROR?)
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 */
};
Note about recoverable errors: I'm thinking to probe() operations here.
Another issue:
should we limit to module operations return code or should we
make things more generic?
Best regards,
--
Francesco Romani - Ikitt ['people always complain, no matther what you do']
IM contact : (email first, Antispam default deny!) icq://27-83-87-867
known bugs : http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase
tiny homepage : http://fromani.exit1.org (see IDEAS if you want send code!)
