The question was due to a typo in a hastily written description;
At 08:55 PM 1/8/2004, Donald Doane wrote:
>The following comment is from apr_lib.h:
>
> * apr_vformatter does not call out to any other code, it is entirely
> * self-contained. This allows the callers to do things which are
> * othe
Thank you for the claification.
Sander Striker wrote:
On Fri, 2004-01-09 at 04:50, Cliff Woolley wrote:
[...]
That seems to say to me that apr_psprintf is in fact threadsafe after all.
:-)
It actually depends on how apr_psprintf is called, pass it the same pool
in two
The following comment is from apr_lib.h:
* apr_vformatter does not call out to any other code, it is entirely
* self-contained. This allows the callers to do things which are
* otherwise "unsafe". For example, apr_psprintf uses the "scratch"
* space at the unallocated end of a block, and
On Fri, 2004-01-09 at 04:50, Cliff Woolley wrote:
[...]
> That seems to say to me that apr_psprintf is in fact threadsafe after all.
> :-)
It actually depends on how apr_psprintf is called, pass it the same pool
in two concurrent threads and it might blow up. Is the apr_psprintf
function otherwi
On Thu, 8 Jan 2004, Donald Doane wrote:
> The following comment is from apr_lib.h:
>
> * apr_vformatter does not call out to any other code, it is entirely
> * self-contained. This allows the callers to do things which are
> * otherwise "unsafe". For example, apr_psprintf uses the "scratch"
>
Where does it say that? httpd uses it extensively, so if it's not, I'd
tend to think we'd have noticed by now...
--Cliff
On Thu, 8 Jan 2004, Donald Doane wrote:
> Okay, will do that, but it's called in
> "flood_easy_reports::easy_process_stats()" and it seems APR
> documentation implies it is
