Since we don't return anything, but rc, from the get_brigade, pass_brigade and fflush, I think the golden solution is to always return rc, but to croak if there is an error and a user didn't bother to check rc (i.e. calling in the void context).

If you are wondering why I'm bothering to change all these APIs, it's in order to make things more perlish. But more important to have as few API functions as possible that allow users to write code that doesn't check return values. This is in order to make our user support life easier and always croak when something is wrong, so users won't submit bug reports, for something that's their code's problem. Not needing to check for errors also makes prototyping much faster and easier to read.

When saying users I refer to developers who use mod_perl 2.0 API.

--
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to