> IMO, I would ask people to be much more conservative with pool
> usage. Don't just go and create/destroy them willy nilly. More
> pools, more confusion ("gee, which pool is this in?"). Create/dest
> of pools is only important within high-level loops that are
> unbounded in size (the subpool is used to impose a bound).
Huh. I had the opposite impression. For instance, it seems to me
like the editor functions in some of the editors are leaking memory
into the editor pool each time some of the functions are called.
That's bad because the whole point of the editor interface is not to
impose space requirements based on the size of the edits being done.
Because memory leaks won't be noticeable until well after our product
goes to 1.0, I'm a bit more concerned about careless pool usage
leading to memory leaks than I am about careless pool usage leading to
memory corruption. Both kind of bugs are hard to fix, but one tends
to manifest itself sooner.
Received on Sat Oct 21 14:36:10 2006