ements (2b). Could you
please review, when you get a chance, to see if this resolves the
problem you reported?
James.
On Jan 19, 2005, at 2:42 PM, Chris Cates wrote:
Hey James,
Thanks very much for the response. I'm definitely in favor of option
(2b).
First of all, I'm out of my le
you've got a somewhat reproducible test, I'd love it if you'd
help me write and/or test 2b.
-jdb
On Jan 19, 2005, at 11:40 AM, Chris Cates wrote:
I have an odd problem that I was wondering if anyone has seen before
or could maybe offer some input on.
I'm using xerces 2.
I have an odd problem that I was wondering if anyone has seen before or
could maybe offer some input on.
I'm using xerces 2.6.0 on MacOS 10.3.7, and my application is
multi-threaded. There are two threads using xerces, each with its own
parser and associated data. I have seen a seg fault a co
ets?
Alberto
At 12.05 28/12/2004 -0600, Chris Cates wrote:
Since I haven't heard anything from anyone on the email below, I was
wondering if anyone would have an issue with me submitting the
following change:
//xerces-c-src_2_6_0/src/xercesc/util/Platforms/MacOS/
MacOSPlatformUtils.cpp
Works great for me. Thanks very much!
-Chris
On Dec 28, 2004, at 1:09 PM, James Berry wrote:
Patch committed. Thanks! Please verify.
-jdb
On Dec 28, 2004, at 10:05 AM, Chris Cates wrote:
Since I haven't heard anything from anyone on the email below, I was
wondering if anyone would have an
ve been meaning to get around to this myself.
Thanks for the patch.
-jdb
On Dec 28, 2004, at 10:05 AM, Chris Cates wrote:
Since I haven't heard anything from anyone on the email below, I was
wondering if anyone would have an issue with me submitting the
following change:
//xe
R_SOCKET)
>#include
587a590,591
> #elif (defined(XML_USE_NETACCESSOR_SOCKET))
> return new SocketNetAccessor;
Comments most welcome!
Thanks!
-Chris
[EMAIL PROTECTED]
On Dec 8, 2004, at 12:38 PM, Chris Cates wrote:
Greetings,
I'm currently using xerces-c 2.6 buil
Greetings,
I'm currently using xerces-c 2.6 built on MacOS X 10.3 with sockets as
net access. (Which works very nicely, btw.)
I was wondering why MacOSPlatformUtils' implementation of
makeNetAccessor() does not create and return a SocketNetAccessor by
default if it sees that the XML_USE_NETACC
