On Fri, 2007-10-19 at 15:05 +1000, Bojan Smojver wrote:
Yeah, that's been the problem of the 1.2 API. In 1.3, we cannot do it
with the same function (API/ABI backward compatibility), but we can
introduce another function (e.g. apr_dbd_open_ex()) that does return an
error.
Perhaps something
That works for me. I worked around it in my code, but thought I would
let the group know about it
so others who use the examples as a starting point would not get bit.
/Daniel
-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 3:03
Daniel May wrote:
Should the function
apr_xml_parser_geterror(apr_xml_parser *parser, char *errbuf, apr_size_t
errbufsize)
crash if apr_xml_parser *parser is not initialized ? That is the case
today. From the examples, it is common to do the following:
rv = apr_xml_parse_file(pool,
Should the function
apr_xml_parser_geterror(apr_xml_parser *parser, char *errbuf, apr_size_t
errbufsize)
crash if apr_xml_parser *parser is not initialized ? That is the case
today. From the examples, it is common to do the following:
rv = apr_xml_parse_file(pool, parser, doc, fd, 2000);
Hello William,
No I am not doing a profile analysis (seems beyond my scope).
I'm new to Linux administration and am trying to get the most recent SVN
and dependencies ( APR , Neon ) and following the instructions given in
the tarball package. I did attempt initially with no explicit
revision 554995 introduced apr_atomic_xchgptr, but did not have the os390
implementation.
This will allow test/testatomic.c at trunk (it tests apr_atomic_xchgptr for
all platforms) to compile and tests successfully on zOS.
Index: atomic/os390/atomic.c
