Re: Why passing a pool to a printf?

Nicolás Lichtmaier wrote:

>
>>> 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? =)

Yes, becasue you'd have to control access to the hash table. Really, it
doesn't make sense to do that.

---------------------------------------------------------------------
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:13:38 2004