Scott Cantor wrote:
Eh, all that's required is another transcoding jump from XMLCh* to
wstring in the XML code wrappers. Irritating and slow, but
not a major complication.
Well, so, I've been punting for a while on actually building a usable
wrapper that's STL container-friendly. Mostly because
On Tue, 5 Oct 2004, Scott Cantor wrote:
>
> I'm sure there are good reasons for why the C++ committee didn't mandate
> UCS-2 for wchar_t, but whatever they were, they've gone a long way in
> convincing the XML community to stay with Java and ignore C++. So I hope it
> was worth it. ;-)
Too many pe
On Tue, 5 Oct 2004, Scott Cantor wrote:
>
> > But you are right, Xerces internally uses
> > UTF-16 strings, and wchar_t isn't a cross-platform storage for
> > UTF-16. The point is that platforms that know this is true (like Windows)
> > would like to see XMLCh==wchar_t, even if they can just cast t
On Mon, 21 Jun 2004, Andre Stock wrote:
>
> Is it possible to change the typedef of XMLCh* to wchar_t*,so that i can
> parse the unicode stream? If this is possible, where can i find the typedef
> of XMLCh*?
Yes it is. This typedef is in the compiler/platform header files. But
you may not want t
On Wed, 26 May 2004, Adam Heinz wrote:
>
> These lines leak memory. If you don't pass an output buffer to transcode, you need
> to XMLString::release() the returned buffer.
Something I wasn't sure on from the documentation. Does transcode reuse
the same buffer and grow as needed or does it allo
On Wed, 19 May 2004, Imran A R (RBIN/EDM1) * wrote:
>
> can you please send me some samples of this ostream method?
struct MyStruct {
int SomeInt;
std::string SomeString;
};
std::ostream& operator<<( std::ostream& os, MyStruct const& ms ) {
os << "";
return os;
}
This does
Imran A R (RBIN/EDM1) * wrote:
Hi
I got it, it is working
But I heard DOM is more memory consumin. Is there any other way?
You can always do it by hand by creating ostream methods for your classes.
Sean
-
To unsubscribe, e-mail: [E
Dan Rosen wrote:
The trouble I'm running into is, when parsing, a buffer in memory for the
characters in this tremendous block of data is being maintained, and is grown
when necessary by XMLBuffer::insureCapacity. This buffer gets so large that
at some point, the allocation in insureCapacity fails,
On Tue, 27 Apr 2004, Adam Heinz wrote:
>
> It sounds like you are doing SAX, yes?
>
> I use a simple list (stack) to maintain state. I tokenize my element
> and attribute names into integers. In some cases, I use a hash table to
> index function pointers by token. In other cases, I just switch (
Is there any way, from within a DocumentHandler, to indicate to the SAX
parser that I don't want parsing to continue? I know I could throw an
exception, but I'd prefer to avoid that if possible.
Sean
-
To unsubscribe, e-mail:
I just ran into a situation where the parsing of one XML document with the
SAX parser might trigger the need to process another XML document
mid-parse. ie. one of the SAX events may need to load and process an XML
file. Assuming I'm using different parser objects, will this work? I
just want to
On Fri, 28 Nov 2003, Gareth Reakes wrote:
>
> You have to register an error handler. All errors get passed
> through it and if you want to throw an exception then you can. Note that
> this is for flexibility - you may want it to throw an exception and stop,
I think the default behavior of th
On Fri, 24 Oct 2003, [iso-8859-1] Carlos Bazílio wrote:
>
> I'm a newbie at Xerces. Since I've started using Xerces, I parsed my XML files using
> parseURI method from DOMBuilder class. Now I wish to parse a XML provided by a
> string (char *). How can I do that using DOMBuilder ? Is DOMInputSour
On Mon, 27 Oct 2003, Ronald Landheer-Cieslak wrote:
>
> Yes.. but only possible with Java (or more generally, when you have a garbage
> collection mechanism in your memory management). I usually write in C or C++
> and don't have the luxury of a memory manager, let alone a garbage collector..
Kind
On Mon, 27 Oct 2003, James Williams - Sun East Coast IR Development wrote:
>
> > When two or more parser instances exist in a process, the instances can
> > be used concurrently, without external synchronization. That is, in an
> > application containing two parsers and two threads, one parser can
On Tue, 14 Oct 2003, jiang lei wrote:
>
> I just did a cvs update and VC7 build for xercesc2_3_0 and got 668
> unresolved external symbols. Is there anything wrong with the project files?
> Or where can I get a working version of 2_3_0?
Yup. There are two source files missing from the lib project
I should probably just dig through the code to find this out, but can
someone tell me how large the "characters" buffer is? I was running
some tests the other day and I noticed it's more than 1k so I thought
I'd ask. I'm expecting to push some decent-sized chunks of data through
this area and am
On Mon, 29 Sep 2003 [EMAIL PROTECTED] wrote:
>
> Can you provide a reference to the part of the standard that supports your
> statement? I believe the 'this' pointer can be used in the
> mem-initializer, as per 12.6.7 and 12.6.8 (which seem to contradict your
> statement).
Oops! You're right. S
Just got the latest copy of the source and noticed this hasn't been
cleared up. The offending files are:
DocumentImpl.cpp
DOMParentNode.cpp
DOMDocumentImpl.cpp
The code that's breaking is similar to this:
DocumentImpl::DocumentImpl(MemoryManager* const manager)
: ParentNode(this)
Problem b
19 matches
Mail list logo
