The state of the state of the Perl stuff

Ok, I now finally get to ask a question... We are probably going to use Xerces stuff at work, and some of the folks involved need to use Perl interfaces. What is the state of the state with the Perl stuff now in the repository vs. what's in the current 1.4 release.   -

RE: [Bug 1329] New - SAX2XMLReaderImpl leaks XMLBuffers

No code should bid on buffers directly, in general, but instead use the supplied buffer bid janitor classes that will insure that the buffers get released upon exit. -- Dean Roddey Software Geek Extraordinaire Portal, Inc [EMAIL PROTECTED] -Original Message- From: [EMAIL PR

[Bug 1329] New - SAX2XMLReaderImpl leaks XMLBuffers

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1329 *** shadow/1329 Thu Apr 12 14:12:44 2001 --- shadow/1329.tmp.26322 Thu Apr 12 14:12:44 2001 *** *** 0 --- 1,127 + ++ + | SAX2XMLReaderImpl

[Bug 1327] New - DOMParser crashes if XML source has damaged structure.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1327 *** shadow/1327 Thu Apr 12 13:38:31 2001 --- shadow/1327.tmp.26246 Thu Apr 12 13:38:31 2001 *** *** 0 --- 1,21 + ++ + | DOMParser crashes

Re: Sax parser errors

Thanks, I will kick myself in the ass now. When creating the MemInputSource I use the correct string but the length of the old string. Sorry Glenn [EMAIL PROTECTED] wrote: > 5 < 7 > > Certainly ought to work. > > I hate to ask the dumb question, but have you tried printing ou

Re: Sax parser errors

5 < 7 Certainly ought to work. I hate to ask the dumb question, but have you tried printing out the contents of that buffer, to make absolutely sure you're parsing what you think you're parsing? (Last time I had one of these "It can't possibly fail" issues, it turned out that I hadn't successfu

Sax parser errors

Hi All, I am using the xerces SAX parser. If I pass the parser the following string in a MemInputBuffer: 5 < 7 I get an error, which I expect. The error is: expected on element name when I pass the parser this string: 5 < 7 I strill get an error, which I don't expect: expected end of tag 'e

RE: memory use / DOM

> -using XMLPlatformUtils::Terminate() at the end. Do you mean at the end of the app or the end of each parse()? If you call it at the end of each parse() then that's the problem. It should only be called at termination of the program, or not at all. -- Dean Roddey Software Geek Extr

Re: [Fwd: RFC: XML::Xalan (was: Re: perl/xalan)] (fwd)

In my opinion, use of Xalan is ok by me, in this context. -scott Edwin Pratomo

Re: [Bug 1321] New - config.guess thinks HPUX 11.00b is a 64bit system

[EMAIL PROTECTED] wrote: > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1321 > > + | DESCRIPTION | > + On that version of OS, sysconf(_SC_KERNEL_BITS) returns 64, even though it's a > + 32 bit version of HPUX. config.guess end

[Bug 1321] New - config.guess thinks HPUX 11.00b is a 64bit system

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1321 *** shadow/1321 Thu Apr 12 08:54:46 2001 --- shadow/1321.tmp.22291 Thu Apr 12 08:54:46 2001 *** *** 0 --- 1,22 + ++ + | config.guess think

memory use / DOM

Hi My C++ app uses the DOM parser to read in a large number of documents one after the other for processing. I'm trying to be very careful about memory usage as the app needs to be reliable and long-running. But despite my efforts, the memory footprint of the app grows by a few K each time a doc

Re: Visual Age and Xerces

What kind of problems? I have STL working with xlC (albeit with a few warnings) finally. Todd - Original Message - From: "Bovone Stefano" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 12, 2001 3:17 AM Subject: Visual Age and Xerces > > Hello everybody. > I'm using

Re: transcode()

But don't forget to delete the char* (in this case valueT), as transcode hands responsibility for that to the caller. John > Gary Marsh wrote: > > Hi Cad; > > Just a guess but I think you probably need to do something > like this: > > DOMString value = newNode.getNodeValue();

Re: memory management

As far as I know, you are correct in thinking that this code would work. However, extreme caution should be taken over using code like this. I am currently working on a project which uses similar reference counting, and bugs in the this code are the hardest bugs we have had to track down. Surely

Visual Age and Xerces

Hello everybody. I'm using Xerces on AIX and Visual Age 4.0; but I have problems compiling a program that uses STL library. The compiler gives errors during the compiling phase. Is this a known problem, or a my Visual Age problem ? Using Visual Age, Xerces and STL do I have to set features diff

Re: memory management

On Wed, Apr 11, 2001 at 12:31:58PM -0400, [EMAIL PROTECTED] wrote: > > >Why can't I 'new' dom objects? Is this wrong practise > >unconditionally, or I only must be very careful? > > Wrong practice pretty much unconditionally, unless you're a parser or > otherwise need to access things in ways th

[Bug 1303] Changed - AttrImpl::setValue with null argument

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1303 *** shadow/1303 Wed Apr 11 17:13:57 2001 --- shadow/1303.tmp.21367 Thu Apr 12 00:34:47 2001 *** *** 41,44 someone chokes on it down the line. On the other hand I agree that behaving as a no-op for that matter doesn

Re: memory management

On Wed, Apr 11, 2001 at 04:26:09PM -0400, Cem Karan wrote: > Anyone who wants to jump in and correct me, please do so. > > Xerces tries to use reference counting wherever possible to > automatically dispose of unused memory in much the same way that Java > does it. If you actually use new and de