I think it'll be more perlish to have:
$ba->destroy;
or even better an implicit DESTROY, rather than having:
APR::Bucket::alloc_destroy($ba);
or (better than above): $ba->alloc_destroy;
OK, so that brings us to the same story as with APR::Pool, some allocs are custom and some aren't. So some need to be destroyed and some must not be destroyed. But if we decide to build a consistent API, I can't see why if we have a slick APR::Pool, have the APR::BucketAlloc clumsy.
-- __________________________________________________________________ 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]
