[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why passing a pool to a printf?

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-05-18 04:12:04 CEST

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

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.