Stas Bekman <[EMAIL PROTECTED]> writes: > Joe, why do we expose $bb->bucket_alloc()?
As I've explained before, the bucket_alloc slot doesn't belong to the brigade, it belongs to some pool. Exposing it is convenient, especially for APR-based libraries which don't care where the bucket allocator actually comes from. > (I've also just made it read-only, since you certainly don't want that > to be writable). Doesn't it sort of makes thing dangerous. If let's > say some bucket_alloc was used to create the brigade, > then a bucket was allocated using that alloc and then the bucket was > moved to a different brigade, and the first one is destroyed. That's a > potential scenario for a problem. No it's not. As I explained before, calling apr_brigade_destroy() on a brigade has no impact on the bucket allocator slot whatsoever. The bucket allocator is only affected by a pool cleanup. Have you forgotten what I wrote when you asked this question last week, or do you disagree with my explanation? -- Joe Schaefer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
