I understand BIND_NOSTART has been in the code since it was first checked
into apache 1.3. I also understand the desire not to break existing
functionality. I can tell you that BIND_NOSTART prevents any C++ module
developer from being able to take advantage of static initialization. I'd be
more
Ian Holsman wrote:
On Sun, 09 Feb 2003 13:28:13 -0800, Jacob Lewallen wrote:
Hi there, I've stumbled on a bug in the apr_queue_t code... When
calling apr_queue_pop to retrieve an item from the queue the call may
block indefinately despite items having been pushed in. Same things goes
for
Just a side note here; although I haven't the faintest idea about the
intricacies of dynamic loading on HP-UX, I _do_ know that in some
situations, even plain C code needs constructor-like initialization when
a shared library is loaded. This leads me to guess that BIND_NOSTART
might be bad even
Can you do us a big favor and please resubmit the patch without any
whitespace changes? That is, only diff what you actually changed. We
No problem. Here she is.
--
jacob lewallen
[EMAIL PROTECTED]
Index: apr_queue.c
===
RCS
