Re: [transcode-devel] using TC_{IMPORT, EXPORT}_* macros in returning values in modules

2006-10-08 Thread Andrew Church
>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 */ >

Re: [transcode-devel] using TC_{IMPORT, EXPORT}_* macros in returning values in modules

2006-10-08 Thread Francesco Romani
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

Re: [transcode-devel] using TC_{IMPORT, EXPORT}_* macros in returning values in modules

2006-10-08 Thread Andrew Church
>Very last commits on encode_X264.c reverted my changes in using returning >values. >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 t

[transcode-devel] using TC_{IMPORT, EXPORT}_* macros in returning values in modules

2006-10-08 Thread Francesco Romani
Hi, Very last commits on encode_X264.c reverted my changes in using returning values. 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 :) Best regards -- Francesco Ro

Re: [transcode-devel] transcode 1.0.3rc0

2006-10-08 Thread Francesco Romani
On Sat, 7 Oct 2006 18:09:18 -0700 Phil Ehrens <[EMAIL PROTECTED]> wrote: > Francesco Romani wrote: > > > > this afternoon/night I've drinked some extra coffee, so I've been capable > > to revamp 1.0.x branch applying *really* urgent hotfixes. > > I appreciate this VERY much Francesco, since toda