Share

Expat XML Parser

Code

Programming Languages: C

License: MIT License

Repositories

browse code, statistics, last commit on 2009-09-29 cvs -d:pserver:anonymous@expat.cvs.sourceforge.net:/cvsroot/expat login

cvs -z3 -d:pserver:anonymous@expat.cvs.sourceforge.net:/cvsroot/expat co -P modulename

Show:

What's happening?

  • OBJEXT and EXEEXT support while building

    version 2.0.1 Add different from *.o object files extension support and executable extention support to Makefile.in It is actual for building expat using cl.exe compiler. The possible candidate for update Makefile.in is attached.

    2009-10-22 18:09:50 UTC by https://www.google.com/accounts

  • Comment: dangling positionPtr after error

    Fixed in xmlparse.c rev. 1.164. Please report back if there are still issues.

    2009-09-29 02:51:49 UTC by kwaclaw

  • Expat XML Parser

    kwaclaw committed patchset 1138 of module expat to the Expat XML Parser CVS repository, changing 1 files.

    2009-09-29 02:49:16 UTC by kwaclaw

  • Comment: dangling positionPtr after error

    Just noticed this is a duplicate of 2518079. However that one was evidently closed because it "stopped happening.".

    2009-09-09 23:20:33 UTC by dvitek

  • dangling positionPtr after error

    I am getting a segv when asking pyexpat to parse some bad xml. I'm not sure whether this is a problem with pyexpat or with expat, but I'm leaning towards expat after finding a (partial?) fix. The stack of the segv is: (gdb) bt #0 0x010245f8 in normal_updatePosition (enc=0x1035fc0, ptr=0x73b000 , end=0x186cc50 "

    2009-09-09 23:09:04 UTC by dvitek

  • Expat XML Parser

    ssolie committed patchset 1137 of module expat to the Expat XML Parser CVS repository, changing 10 files.

    2009-08-08 03:48:55 UTC by ssolie

  • Add support for EXEEXT

    The Expat 2.0.1 Makefile.in template file does not contain support for the autoconf EXEEXT macro variable. I've attached a unidiff that adds this support. No changes to the configure script are required; the necessary logic is already present. I've tested these changes on a Stratus VOS system, which has a required executable extension. The changes are harmless on an operating system that does...

    2009-07-02 18:58:49 UTC by paulg73

  • Comment: expat memory consumption issue - advise needed

    I looked at your C code. The XmlNodeRef class gave it away, you are not actually using Expat directly, but apparently some DOM wrapper around it. This will build an in-memory representation of the XML file and consequently consume several times as much memory as the file size. If you check the Expat reference document you will see that Expat based code uses call-backs to inform the...

    2009-04-02 12:07:56 UTC by kwaclaw

  • Comment: expat memory consumption issue - advise needed

    Karl, The file is around 3MB compressed. I can send it to you via email if you need it.

    2009-04-02 03:51:11 UTC by alexmanovbg

  • Comment: expat memory consumption issue - advise needed

    Sorry I could not attach it. Here is the C application code: #include #include #include #include #include #include "xml.h" //// Load() of CRatingEngine int LoadXML ( const char *szFileName) { FILE *pXMLFile = fopen ( szFileName, "rb"); if ( !pXMLFile) { printf ("Load: File name %s is not exists\n"...

    2009-04-02 03:44:11 UTC by alexmanovbg