Who is the maintainer of Xerces-C?
--
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
"Jason E. Stewart" wrote:
>
> "Murray Cumming" <[EMAIL PROTECTED]> writes:
>
> > "Arnold, Curt" wrote:
> > >
> > > I haven't been following this thread and it troubles me that
> > > appears that it would require touching every single include of a
> > > Xerces header file at least in applications
Title: memory leaks in Xerces-C++ 1.5.0 version
Hi,
I found two places may have memory leak problem.
First, in src/validators/common/DFAContentModel.cpp Line 464 function DFAContentModel::buildDFA().
statement:
QName* qname = new QName(XMLUni::fgZeroLenString, XML
Hi,
I'm trying to install Xerces-win32 on my machine (equipped with windows 2000).
Is it possible ? If yes, what is the procedure ?
Thanks
Best regards
Nicolas Kuznik
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Hi,
We have an Application which needs to be compiled on Solaris 8.
Could u tell me if it is safe to use Xerces-c library which is Built on
Solaris 7 and Build our Application on Solaris 8.
Or Do we need to build xerces-c on Solaris 8 and then Build the
Application.
Thanx in Advance,
Re
"Arnaud Le Hors" <[EMAIL PROTECTED]> writes:
> "Jason E. Stewart" wrote:
> >
> > "Murray Cumming" <[EMAIL PROTECTED]> writes:
> >
> ...
> > > Actually, it *would* be better to just rename src to xercesc and stop
> > > copying the headers into include.
> >
> > That does seem like an elegant sol
> No, I have said several times that this will not require any
> existing apps to change the way that they #include the
> Xerces-C++ headers. Read the thread.
Actually, I had read every message in the thread before posting. I had not been
following the thread but started to see things that lo
"Jason E. Stewart" wrote:
>
> "Murray Cumming" <[EMAIL PROTECTED]> writes:
>
...
> > Actually, it *would* be better to just rename src to xercesc and stop
> > copying the headers into include.
>
> That does seem like an elegant solution.
>
> One drawback is that it does mean mucking with the C
Hi, all:
I want to compile SAX2Print alone with
g++. What things, at least, should I feed to g++ at the command line? I use
binary form of xerces-c 1.5.1.
Thanks.
~Frank
search the mailing-list archive for DOMSerializer.cpp
Someone really ought to include it in the dist ...
Timothy R Aldrich
CREDIT | FIRST
SUISSE | BOSTON
Global Web Services (NYC)
Voice: (212) 325-8652
Fax:(212) 325-9596
E-mail: mailto:[EMAIL PROTECTED]
Pager:
>Is there any API in Xerces C++ to write from DOM to an external (ASCII)
file
>to create an XML document? Looking for something similar to XMLWriter in
JDOM.
Take a look at http://xml.apache.org/xerces-c/domprint.html for an example.
-
Is there any API in Xerces C++ to write from DOM to an external (ASCII) file
to create an XML document? Looking for something similar to XMLWriter in JDOM.
Thanks.
Sharat Shetty
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
BDY.RTF
The StdInInputSource
has been broken in 1.5.1 and the sample that demonstrates its usage terminates with
an error.
BDY.RTF
"J. J. Merelo" <[EMAIL PROTECTED]> writes:
> and the second, it's very un-PERL-like; coming from PERL, where
> there's a wonderful XML::Simple module that converts a whole XML doc
> into a tree
You could always use XML::Xerces which is the perl interface to
Xerces-C, available at xml.apache.org.
"Murray Cumming" <[EMAIL PROTECTED]> writes:
> Murray Cumming wrote:
> >
> > Tinny Ng wrote:
> > > I just worry, if we do this, will we eventually be asked to add "xercesc" to all
> > > the folders
> > > => include/xercesc
> > > => samples/xercesc
> > > => bin/xercesc
> > > => lib/xercesc
> > >
"Murray Cumming" <[EMAIL PROTECTED]> writes:
> "Arnold, Curt" wrote:
> >
> > I haven't been following this thread and it troubles me that
> > appears that it would require touching every single include of a
> > Xerces header file at least in applications (and possibly in the
> > Xerces code base
Murray Cumming wrote:
>
> > I suggest, if you change, to simply use either xerces or Xerces (my
> > preference).
>
> I just used the principle that more information is better.
Wait a minute!
> --
> Murray Cumming
> www.murrayc.com
^
> [EMAIL PROTECTED]
^
What do I see here?
> Ram Sadasiv wrote:
> >
> > In addition to being "un-STL-like" and "un-PERL-like", when you get
into
> > the XMLPlatformUtils and the framework's insistence to returning memory
> > managed objects rather than pointers, it gets kind of "un-C++-like".
> >
>
> Right-on... I was surprised to see get
The question of abandoning support for compilers that aren't quite up to
modern standards comes up periodically. So far, it has always turned out
that one or another supported platform still doesn't have a compiler with
adequate support for the language features we'd like to take advantage of.
(O
Its a lot easier to port from Java (Xerces-J) if you use a "Java-like"
approach. That means smart pointers, no templates etc.
Jim
> -Original Message-
> From: J. J. Merelo [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 16, 2001 12:30 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Barrage
Ram Sadasiv wrote:
>
> In addition to being "un-STL-like" and "un-PERL-like", when you get into
> the XMLPlatformUtils and the framework's insistence to returning memory
> managed objects rather than pointers, it gets kind of "un-C++-like".
>
Right-on... I was surprised to see getChild return c
"J. J. Merelo" wrote:
>
> Hi,
> Just compiled my first xerces-c++ program, and so far, so good, but I
> found some things I didn't like. The first thing is that it's very
> un-STL-like, that is, STL is barely used (for instance, DOMString is
> used instead of the STL string, which already
In addition to being "un-STL-like" and "un-PERL-like", when you get into
the XMLPlatformUtils and the framework's insistence to returning memory
managed objects rather than pointers, it gets kind of "un-C++-like".
But, as you point out, options are few... Also, given the number of
target operatin
Hi,
Just compiled my first xerces-c++ program, and so far, so good, but I
found some things I didn't like. The first thing is that it's very
un-STL-like, that is, STL is barely used (for instance, DOMString is
used instead of the STL string, which already takes into account locale
and all
[EMAIL PROTECTED] wrote:
>
> >Anything that makes it difficult for me to build an app against the Xerces
> >source tree or a binary release without code changes, doesn't sound like a
> >good thing.
>
> Would one way to allow folks to take their time moving to the new includes
> be to set up file
this is how ICU solved the problem.
Herb...
Joseph
>Anything that makes it difficult for me to build an app against the Xerces
>source tree or a binary release without code changes, doesn't sound like a
>good thing.
Would one way to allow folks to take their time moving to the new includes
be to set up files with the old names that just include
Murray Cumming wrote:
>
> Tinny Ng wrote:
> > I just worry, if we do this, will we eventually be asked to add "xercesc" to all
> > the folders
> > => include/xercesc
> > => samples/xercesc
> > => bin/xercesc
> > => lib/xercesc
> > => doc/xercesc
> > . ??
>
> I don't understand why these othe
Arnaud Le Hors wrote:
>
> As far as I am concerned I don't have a pb with moving all the headers
> into a specific subdirectory but I must say I really don't like the name
> "xercesc". Why do we need a 'c' here? You're not concerned that it might
> conflict with xercesj headers are you? ;-)
Sure
31 matches
Mail list logo
