Re: Why passing a pool to a printf?

>>Why not creating and destroying a pool with each printf?
>>
>>
>
>Creating and destroying a pool is moderately expensive.
>
>Also, we don't like creating pools entirely from scratch. This way, the
>printf implementation can allocate memory and not worry about cleaning
>it up if it has to error out.
>
>

Oh, I see...

Would it be overkill to maintain a hashtable with pools, with one pool
per thread? =)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 18 04:11:16 2004