From abhasin at buffalo.edu  Sat Oct  1 08:00:21 2005
From: abhasin at buffalo.edu (Anmol Bhasin)
Date: Sat, 01 Oct 2005 02:00:21 -0400
Subject: [Expat-discuss] Strange Runtime Problem
Message-ID: <433E25F5.3000200@buffalo.edu>

Hello all,

I have been using the EXPAT for a while, however this time around I am 
facing a stange error.
I am using the expat library in the dynamic link mode, with my code just 
including expat.h.

This is a small C++ Program with once class which is essentially using 
expat as the parser for some XML documents.  Here is a snippet of my ant 
file :

 <target name="CorpusReader" depends="init">
           <echo>Building Object for CorpusReader ...</echo>
          <exec executable="g++">
              <arg line="-g -I${include} -I${expat_inc} -L${lib_expat} 
-lexpat -o build/CorpusReader"/>
            <arg file="${src}/CorpusReader.cpp"/>
          </exec>
</target>


where lib_expat is <expat_dir>/lib
and expat_inc is <expat_dir>/include

The compile goes fine, however during the running of the Program I get a 
SEG FAULT at the point where the first chunk of my data is sent across 
XML_Parse. The GDB reads

Parsing 
File../trec/software/ConceptGraphBuilder/transitions/data/temp/layers.xml

Program received signal SIGSEGV, Segmentation fault.
0x4001a798 in XML_GetBuffer (parser=0x0, len=1024) at lib/xmlparse.c:1465
1465    lib/xmlparse.c: No such file or directory.
        in lib/xmlparse.c
Current language:  auto; currently c

I can't figure out for nuts the problem. Any help would be appreciated.

regards,
Anmol

  





From reid at x10sys.com  Sat Oct  1 08:56:44 2005
From: reid at x10sys.com (Reid Spencer)
Date: Fri, 30 Sep 2005 23:56:44 -0700
Subject: [Expat-discuss] Strange Runtime Problem
In-Reply-To: <433E25F5.3000200@buffalo.edu>
References: <433E25F5.3000200@buffalo.edu>
Message-ID: <433E332C.1030407@x10sys.com>

See below ...

Anmol Bhasin wrote:
> Hello all,
> 
> I have been using the EXPAT for a while, however this time around I am 
> facing a stange error.
> I am using the expat library in the dynamic link mode, with my code just 
> including expat.h.
> 
> This is a small C++ Program with once class which is essentially using 
> expat as the parser for some XML documents.  Here is a snippet of my ant 
> file :
> 
>  <target name="CorpusReader" depends="init">
>            <echo>Building Object for CorpusReader ...</echo>
>           <exec executable="g++">
>               <arg line="-g -I${include} -I${expat_inc} -L${lib_expat} 
> -lexpat -o build/CorpusReader"/>
>             <arg file="${src}/CorpusReader.cpp"/>
>           </exec>
> </target>
> 
> 
> where lib_expat is <expat_dir>/lib
> and expat_inc is <expat_dir>/include
> 
> The compile goes fine, however during the running of the Program I get a 
> SEG FAULT at the point where the first chunk of my data is sent across 
> XML_Parse. The GDB reads
> 
> Parsing 
> File../trec/software/ConceptGraphBuilder/transitions/data/temp/layers.xml
> 
> Program received signal SIGSEGV, Segmentation fault.

This means you de-referenced a null, or otherwise invalid pointer.

> 0x4001a798 in XML_GetBuffer (parser=0x0, len=1024) at lib/xmlparse.c:1465

Lo and behold, you'ved called XML_GetBuffer and passed in a null pointer as the 
parser structure.  Review your code and pass in the correct parser address. Did 
you create one?

> 1465    lib/xmlparse.c: No such file or directory.
>         in lib/xmlparse.c
> Current language:  auto; currently c
> 
> I can't figure out for nuts the problem. Any help would be appreciated.
> 
> regards,
> Anmol
> 

From paul at toddsoftware.com  Mon Oct  3 09:41:49 2005
From: paul at toddsoftware.com (Paul Todd)
Date: Mon, 3 Oct 2005 08:41:49 +0100
Subject: [Expat-discuss] Expat parser on Symbian platform
In-Reply-To: <913179aa05092904474b013740@mail.gmail.com>
Message-ID: <006901c5c7ed$e9fc74a0$6500000a@PaulsLaptop>

Hi,

You can download a copy of the port from toddsoftware.com, look in the
download section or I can email you the zip file if you prefer 

-----Original Message-----
From: expat-discuss-bounces at libexpat.org
[mailto:expat-discuss-bounces at libexpat.org] On Behalf Of Aman Arora
Sent: 29 September 2005 12:47
To: expat-discuss at libexpat.org
Subject: [Expat-discuss] Expat parser on Symbian platform

hi,

I found this query on the list, posted some time back:
 Hi,

I am new on Symbian platform and need to use XML parser on it.
I had used expat parser on other platforms.
Can it be used on Symbian series 60 platform also.
Please send me some information on this.

Thanks and Regards

Vivek

I was unable to find any answers to this query on the list. Currently I am
also involved in a similar activity, Can someone please share some
information regarding this?

rgds
aman
_______________________________________________
Expat-discuss mailing list
Expat-discuss at libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss



From raphael.bossek at gmx.de  Tue Oct  4 07:41:06 2005
From: raphael.bossek at gmx.de (Raphael Bossek)
Date: Tue, 4 Oct 2005 07:41:06 +0200
Subject: [Expat-discuss] Expat with UTF-32 support (as implemented in
	4Suite.org)
Message-ID: <20051004074106.33a8e57f.raphael.bossek@gmx.de>

Hi expat team,

first, I'm the 4suite.org Debian GNU/Linux maintainer. 4suite is a
XML package for Python using expat today with UTF-32 support. And
here is the problem. Using the official libexpat library will not
work with 4suite.org due to missing UTF-32 support. The 4suite.org
team extended the expat implementation for their project themself.

I'm interested in makeing the UTF-32 support part of the upcomming
2.0 release. Before making the public I would like to discuss the
problems about this extension. I'l like to know if such extension
would be accepted before 2.0 release.

Without the UTF-32 support in libexpat it will be mutch harder for
me to maintain 4suite.org package for Debian GNU/Linux. The usage
for libexpat instead of staticly linking the 4suite.org extension
into the Python modules is mandatory for mod_python environments.
We have to make sure only one version of expat symbols is loaded
into memory.

Any idears are welcome. In the meantime I'l investigate the patch
done by the 4suite.org team and make a patch agains latest CVS.
I've also see MSVC 6.0 support in it. Is there any interest in it?

-- 
Raphael Bossek
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.libexpat.org/pipermail/expat-discuss/attachments/20051004/cf061ebd/attachment.pgp

From karl at waclawek.net  Tue Oct  4 15:22:42 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Tue, 04 Oct 2005 09:22:42 -0400
Subject: [Expat-discuss] Expat with UTF-32 support (as implemented in
In-Reply-To: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
Message-ID: <43428222.5070809@waclawek.net>

Raphael Bossek wrote:

>Hi expat team,
>
>first, I'm the 4suite.org Debian GNU/Linux maintainer. 4suite is a
>XML package for Python using expat today with UTF-32 support. And
>here is the problem. Using the official libexpat library will not
>work with 4suite.org due to missing UTF-32 support. The 4suite.org
>team extended the expat implementation for their project themself.
>
>I'm interested in makeing the UTF-32 support part of the upcomming
>2.0 release. Before making the public I would like to discuss the
>problems about this extension. I'l like to know if such extension
>would be accepted before 2.0 release.
>  
>
In principle yes, but it depends on how invasive the patch is, and how 
it affects the existing
functionality. In any case I would say we would rather release it as 
1.95.9, to give it some public
exposure and find possible bugs.

>Without the UTF-32 support in libexpat it will be mutch harder for
>me to maintain 4suite.org package for Debian GNU/Linux. The usage
>for libexpat instead of staticly linking the 4suite.org extension
>into the Python modules is mandatory for mod_python environments.
>We have to make sure only one version of expat symbols is loaded
>into memory.
>
>Any idears are welcome. In the meantime I'l investigate the patch
>done by the 4suite.org team and make a patch agains latest CVS.
>I've also see MSVC 6.0 support in it. Is there any interest in it?
>  
>

Yes, let us have a look at it.

I hope Fred reads this as well - haven't heard from him in a while.

Karl

From jeremy.kloth at fourthought.com  Tue Oct  4 17:23:02 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Tue, 4 Oct 2005 09:23:02 -0600
Subject: [Expat-discuss] [4suite-dev] Re: Expat with UTF-32 support (as
	implemented in
In-Reply-To: <43428222.5070809@waclawek.net>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
	<43428222.5070809@waclawek.net>
Message-ID: <200510040923.02967.jeremy.kloth@fourthought.com>

I will start off with some clarification as to what Raphael is saying is 
"UTF-32 support".  The UTF-32 (or UCS-4, pick your name) support is for 
*internal* encoding only.  That is, for non-Expat hackers, the encoding of 
XML_Char strings.

On Tuesday 04 October 2005 7:22 am, Karl Waclawek wrote:
> Raphael Bossek wrote:
> >Hi expat team,
> >
> >first, I'm the 4suite.org Debian GNU/Linux maintainer. 4suite is a
> >XML package for Python using expat today with UTF-32 support. And
> >here is the problem. Using the official libexpat library will not
> >work with 4suite.org due to missing UTF-32 support. The 4suite.org
> >team extended the expat implementation for their project themself.
> >
> >I'm interested in makeing the UTF-32 support part of the upcomming
> >2.0 release. Before making the public I would like to discuss the
> >problems about this extension. I'l like to know if such extension
> >would be accepted before 2.0 release.
>
> In principle yes, but it depends on how invasive the patch is, and how
> it affects the existing
> functionality. In any case I would say we would rather release it as
> 1.95.9, to give it some public
> exposure and find possible bugs.

A raw patch against the 4Suite CVS would be somewhat invasive as I also added 
a few optimization tweaks while implementing internal UTF-32/UCS-4 support.

> >Without the UTF-32 support in libexpat it will be mutch harder for
> >me to maintain 4suite.org package for Debian GNU/Linux. The usage
> >for libexpat instead of staticly linking the 4suite.org extension
> >into the Python modules is mandatory for mod_python environments.
> >We have to make sure only one version of expat symbols is loaded
> >into memory.
> >
> >Any idears are welcome. In the meantime I'l investigate the patch
> >done by the 4suite.org team and make a patch agains latest CVS.
> >I've also see MSVC 6.0 support in it. Is there any interest in it?

Thankfully, the patch should be only my changes as I sync'ed to CVS before 
working on the changes.

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From jeremy.kloth at fourthought.com  Tue Oct  4 17:37:50 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Tue, 4 Oct 2005 09:37:50 -0600
Subject: [Expat-discuss] Expat with UTF-32 support (as implemented in
	4Suite.org)
In-Reply-To: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
Message-ID: <200510040937.50915.jeremy.kloth@fourthought.com>

On Monday 03 October 2005 11:41 pm, Raphael Bossek wrote:
> Without the UTF-32 support in libexpat it will be mutch harder for
> me to maintain 4suite.org package for Debian GNU/Linux. The usage
> for libexpat instead of staticly linking the 4suite.org extension
> into the Python modules is mandatory for mod_python environments.
> We have to make sure only one version of expat symbols is loaded
> into memory.

It will make no difference if the platform's libexpat would have this support 
unless it was compiled with the same settings for XML_Char as Python does for 
Py_UNICODE.  By doing that, no transcoding is required to go from Expat 
strings to Python unicode objects, a large performance boost.

Linking to libexpat is only required for ELF systems not using symbol 
visibility (GCC 4 or 3.4+patch).  However, until Python gets updated to 
support that, it is in apache/mod_python's hands to do so.

> Any idears are welcome. In the meantime I'l investigate the patch
> done by the 4suite.org team and make a patch agains latest CVS.
> I've also see MSVC 6.0 support in it. Is there any interest in it?

One idea to solve this constant PITA wrt mod_python/apache would be a way to 
define a "prefix" for all exported symbols.  So, for example in expat.h, 
instead of:

XMLPARSEAPI(XML_Parser)
XML_ParserCreate(const XML_Char *encoding);

it could be something like:

XMLPARSEAPI(XML(Parser))
XML(ParserCreate)(const XML_Char *encoding);

where:

#define XML_PREFIX XML
#define XML(name) XML_PREFIX#_#name

Just a thought.

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From karl at waclawek.net  Tue Oct  4 19:33:34 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Tue, 04 Oct 2005 13:33:34 -0400
Subject: [Expat-discuss] Expat with UTF-32 support (as implemented in
In-Reply-To: <200510040937.50915.jeremy.kloth@fourthought.com>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
	<200510040937.50915.jeremy.kloth@fourthought.com>
Message-ID: <4342BCEE.3070208@waclawek.net>

Jeremy Kloth wrote:

>One idea to solve this constant PITA wrt mod_python/apache would be a way to 
>define a "prefix" for all exported symbols.  So, for example in expat.h, 
>instead of:
>
>XMLPARSEAPI(XML_Parser)
>XML_ParserCreate(const XML_Char *encoding);
>
>it could be something like:
>
>XMLPARSEAPI(XML(Parser))
>XML(ParserCreate)(const XML_Char *encoding);
>
>where:
>
>#define XML_PREFIX XML
>#define XML(name) XML_PREFIX#_#name
>  
>
Jeremy,

are there any drawbacks to this?

I also seem to rememeber we once discussed a related issue on the list
where there was a need to have both versions of libexpat (UTF-8 and UTF-16)
loaded at the same time. This is not an issue on Windows, but apparently 
on Linux.

If we do anything about the above, we should cover the old issue as well.
However, for details I have to defer to those who are more knowledgable 
on Linux.

Since Fred (the Expat team leader) seems to have dropped out of sight, I 
would be
willing to commit a solution that is agreed upon by a group of knowledgable
Linux/Expat users like yourself, even if I don't completely understand it.

Karl


From karl at waclawek.net  Tue Oct  4 19:55:15 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Tue, 04 Oct 2005 13:55:15 -0400
Subject: [Expat-discuss] Expat with UTF-32 support (as implemented in
In-Reply-To: <4342BCEE.3070208@waclawek.net>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
	<200510040937.50915.jeremy.kloth@fourthought.com>
	<4342BCEE.3070208@waclawek.net>
Message-ID: <4342C203.5030409@waclawek.net>

Karl Waclawek wrote:

>
> If we do anything about the above, we should cover the old issue as well.
> However, for details I have to defer to those who are more 
> knowledgable on Linux.

A link to the old issue is here: bug (feature request) # 1048448 
http://sourceforge.net/tracker/index.php?func=detail&aid=1048448&group_id=10127&atid=110127

Karl

From jeremy.kloth at fourthought.com  Tue Oct  4 20:18:49 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Tue, 4 Oct 2005 12:18:49 -0600
Subject: [Expat-discuss] [4suite-dev] Expat with UTF-32 support (as
	implemented in 4Suite.org)
In-Reply-To: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
Message-ID: <200510041218.49662.jeremy.kloth@fourthought.com>

On Monday 03 October 2005 11:41 pm, Raphael Bossek wrote:
> Without the UTF-32 support in libexpat it will be mutch harder for
> me to maintain 4suite.org package for Debian GNU/Linux. The usage
> for libexpat instead of staticly linking the 4suite.org extension
> into the Python modules is mandatory for mod_python environments.
> We have to make sure only one version of expat symbols is loaded
> into memory.

Just for an update, I've checked in build support code to limit the symbols 
exported from the cDomlettec.so Python module.  It should now be able to be 
used within mod_python without conflicts (at least on platforms that have a 
fairly recent toolchain (2003+).

Raphael, please try latest CVS without applying the patch to build against 
libexpat.  Is there someplace that lists a process that would reproduce the 
conflict/error within mod_python that prompted the patch in the first place?  
I would really like to be able to test this myself as I now run on a 
Debian-based distro (Kubuntu).

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From jeremy.kloth at fourthought.com  Tue Oct  4 21:25:41 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Tue, 4 Oct 2005 13:25:41 -0600
Subject: [Expat-discuss] [4suite-dev] Expat with UTF-32 support (as
	implemented in 4Suite.org)
In-Reply-To: <200510041218.49662.jeremy.kloth@fourthought.com>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
	<200510041218.49662.jeremy.kloth@fourthought.com>
Message-ID: <200510041325.42143.jeremy.kloth@fourthought.com>

On Tuesday 04 October 2005 12:18 pm, Jeremy Kloth wrote:
> Raphael, please try latest CVS without applying the patch to build against
> libexpat.  Is there someplace that lists a process that would reproduce the
> conflict/error within mod_python that prompted the patch in the first
> place? I would really like to be able to test this myself as I now run on a
> Debian-based distro (Kubuntu).

Just an update.  As tested on my local machine, mod_python scripts now 
successfully run with my build time changes.  Before they would die with a 
RuntimeError.

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From raphael.bossek at gmx.de  Tue Oct  4 22:40:45 2005
From: raphael.bossek at gmx.de (Raphael Bossek)
Date: Tue, 4 Oct 2005 22:40:45 +0200
Subject: [Expat-discuss] Expat with UTF-32 support (as implemented in
	4Suite.org)
In-Reply-To: <200510041218.49662.jeremy.kloth@fourthought.com>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
	<200510041218.49662.jeremy.kloth@fourthought.com>
Message-ID: <20051004224045.003a84e6.raphael.bossek@gmx.de>

Hi Jeremy,

thx again for your fast respond to my new suggestion.

> Just for an update, I've checked in build support code to limit the
> symbols  exported from the cDomlettec.so Python module.  It should now
> be able to be  used within mod_python without conflicts (at least on
> platforms that have a  fairly recent toolchain (2003+).

Ok, I'l check this as soon as a new CVS snapshot file exists.

> Raphael, please try latest CVS without applying the patch to build
> against  libexpat.  Is there someplace that lists a process that would
> reproduce the  conflict/error within mod_python that prompted the
> patch in the first place?   I would really like to be able to test
> this myself as I now run on a  Debian-based distro (Kubuntu).

Please refer to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275097
to get a contact address and the history of the mod_python problem.
As soon as I've time I will contact Mirko (original reporter of this problem)
for help in testing. Maybe he has time for us/me ;)

Do you think it make sense to contribute your extension of libexpat upstream?

-- 
Raphael Bossek
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.libexpat.org/pipermail/expat-discuss/attachments/20051004/c7c4762b/attachment.pgp

From jeremy.kloth at fourthought.com  Tue Oct  4 23:36:23 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Tue, 4 Oct 2005 15:36:23 -0600
Subject: [Expat-discuss] [4suite-dev] Re: Expat with UTF-32 support (as
	implemented in 4Suite.org)
In-Reply-To: <20051004224045.003a84e6.raphael.bossek@gmx.de>
References: <20051004074106.33a8e57f.raphael.bossek@gmx.de>
	<200510041218.49662.jeremy.kloth@fourthought.com>
	<20051004224045.003a84e6.raphael.bossek@gmx.de>
Message-ID: <200510041536.23709.jeremy.kloth@fourthought.com>

On Tuesday 04 October 2005 2:40 pm, Raphael Bossek wrote:
> Do you think it make sense to contribute your extension of libexpat
> upstream?

Sure, that is not a problem.  It is whether or not it is stable as Expat is 
very near 2.0.  I believe I groked the relavent code correctly and it seems 
to work just fine in 4Suite across various configurations.

I'll gladly answer any questions Karl or other maintainers have with my 
particular implementation if they are interested.

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From jgaa at jgaa.com  Thu Oct  6 09:22:30 2005
From: jgaa at jgaa.com (Jarle Aase)
Date: Thu, 06 Oct 2005 09:22:30 +0200
Subject: [Expat-discuss] Error: must not undeclare prefix
Message-ID: <4344D0B6.4000302@jgaa.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi list,

I'm getting this error from XML_ParseBuffer(). The XML-file I'm reading
is validated OK by the "Cooktop" XML editor I'm using. Does anyone know
what this error mean? (I get the same error from XML_Parse()).

I'm having the problem when I try to load an XML-file from a shared
library under Windows and also under Debian GNU/Linux (AMD64 build).

Jarle
- --
Jarle Aase                      email: jgaa at jgaa.com
Author of freeware.             http://www.jgaa.com
                                news:alt.comp.jgaa

War FTP Daemon:     http://www.warftp.org
War FTP Daemon FAQ: http://www.warftp.org/faq/warfaq.htm
Jgaa's PGP key:     http://war.jgaa.com/pgp
NB: If you reply to this message, please include all relevant
information from the conversation in your reply. Thanks.
<<< no need to argue - just kill'em all! >>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDRNC2fFWZoih9A8QRAtrtAJwOC9/p1eyTy5qeu3cmfj6M9GC8KQCfcsjT
YHgdTSsPt3/0vt/d1tqv5lY=
=XCwY
-----END PGP SIGNATURE-----

From akumar at kodiaknetworks.com  Thu Oct  6 12:42:57 2005
From: akumar at kodiaknetworks.com (Ajit Kumar)
Date: Thu, 6 Oct 2005 16:12:57 +0530
Subject: [Expat-discuss] Expat not parsing this Tag
Message-ID: <000801c5ca62$b7b7d0d0$ac02a8c0@Ajit>

 
 
Hi,
I am facing a problem while parsing one xml document, which has a tag
like this-
<delete-evt
nselecing="a-list[@name="friends"]/point[@myip="ajit at yahoo.com"]"></
delete-evt>
Expat is exiting as soon as it visits this tag. Giving the error code to
be "not well-formed". 
 
If I change the same tag as this (after removing the internal quotes)-
<delete-evt
nselecing="a-list[@name=friends]/point[@myip=ajit at yahoo.com]"></
delete-evt>
the expat has no problem in parsing the above changed Tag.
 
I will be thankful for any solution that will allow me to parse the Tag
in its first original form.
 
Thanks Ajit
 

From rolf at pointsman.de  Thu Oct  6 13:26:14 2005
From: rolf at pointsman.de (rolf@pointsman.de)
Date: Thu, 6 Oct 2005 13:26:14 +0200 (CEST)
Subject: [Expat-discuss] Expat not parsing this Tag
In-Reply-To: <000801c5ca62$b7b7d0d0$ac02a8c0@Ajit>
Message-ID: <20051006112617.E68448C4C8@pointsman.pointsman.de>


On  6 Oct, Ajit Kumar wrote:
> I am facing a problem while parsing one xml document, which has a tag
> like this-
> <delete-evt
> nselecing="a-list[@name="friends"]/point[@myip="ajit at yahoo.com"]"></
> delete-evt>
> Expat is exiting as soon as it visits this tag. Giving the error code to
> be "not well-formed". 

Expat is right. See production 10 of the XML recommendation. If you
use '"', to delimit attribute values, you can't use a literal '"' within the
attribute value, as you did.

> If I change the same tag as this (after removing the internal quotes)-
> <delete-evt
> nselecing="a-list[@name=friends]/point[@myip=ajit at yahoo.com]"></
> delete-evt>
> the expat has no problem in parsing the above changed Tag.
>  
> I will be thankful for any solution that will allow me to parse the Tag
> in its first original form.

The original form isn't well-formed XML, every compliant XML parser
*must* report error.

You've mainly two options. Since your attribute value looks like an
XPath expr, just use single quotes inside the XPath expr (that is fine
with every XPath engine)

<delete-evt
nselecing="a-list[@name='friends']/point[@myip='ajit at yahoo.com']"></
delete-evt>

or escape your double quotes as usual

<delete-evt
nselecing="a-list[@name=&quot;friends&quot;]/point[@myip=&quot;ajit at yahoo.com&quot;]"></
delete-evt>

rolf



From karl at waclawek.net  Thu Oct  6 15:00:37 2005
From: karl at waclawek.net (Karl Waclawek)
Date: Thu, 06 Oct 2005 09:00:37 -0400
Subject: [Expat-discuss] Error: must not undeclare prefix
In-Reply-To: <4344D0B6.4000302@jgaa.com>
References: <4344D0B6.4000302@jgaa.com>
Message-ID: <43451FF5.3070208@waclawek.net>

Jarle Aase wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi list,
>
>I'm getting this error from XML_ParseBuffer(). The XML-file I'm reading
>is validated OK by the "Cooktop" XML editor I'm using. Does anyone know
>what this error mean? (I get the same error from XML_Parse()).
>
>I'm having the problem when I try to load an XML-file from a shared
>library under Windows and also under Debian GNU/Linux (AMD64 build).
>  
>

If I recall correctly, under the XML Namespaces 1.0 specification you 
can only undeclare
the default namespace. If you try to undeclare another namespace/prefix, 
you would get
this error.

Karl

From raphael.bossek at gmx.de  Tue Oct 11 22:59:18 2005
From: raphael.bossek at gmx.de (Raphael Bossek)
Date: Tue, 11 Oct 2005 22:59:18 +0200
Subject: [Expat-discuss] UTF32 support from 4suite.org for libexpat
Message-ID: <20051011225918.4f2b547e.raphael.bossek@gmx.de>

Hi folks,

as mentioned before you will find a patch created by me
from the 4suite.org sources against latest CVS.

-- 
Raphael Bossek
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: utf32cvs.diff
Url: http://mail.libexpat.org/pipermail/expat-discuss/attachments/20051011/f0280864/utf32cvs.diff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.libexpat.org/pipermail/expat-discuss/attachments/20051011/f0280864/attachment.pgp

From luoy at muohio.edu  Thu Oct 13 19:35:05 2005
From: luoy at muohio.edu (Frank Y.F. Luo)
Date: Thu, 13 Oct 2005 13:35:05 -0400
Subject: [Expat-discuss] installation error on Mac OS X
Message-ID: <JPEBJPEEJLOIKOHFOFEDAEHFCMAA.luoy@muohio.edu>

I received this error, anyone has idea?

$ make
/bin/sh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H   -I./lib -I. -no-undefined -version-info 5:0:5 -rpath /usr/local/lib  -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo
/usr/bin/libtool: for architecture: cputype (16777234) cpusubtype (0) file: -lc is not an object file (not allowed in a library)
/usr/bin/libtool: for architecture: cputype (16777234) cpusubtype (0) file: -lSystem is not an object file (not allowed in a library)


Thanks

Frank

From raphael.bossek at gmx.de  Fri Oct 14 07:44:26 2005
From: raphael.bossek at gmx.de (Raphael Bossek)
Date: Fri, 14 Oct 2005 07:44:26 +0200
Subject: [Expat-discuss] Patch for SF feature request #1048448
Message-ID: <20051014074426.5b12ce18.raphael.bossek@gmx.de>

Hi Karl,

as you mentioned before we should consider the sourceforge.net
feature request #1048448. There are today incompatibilites for
applications linking agains different variantes of libexpat:
 * wchar_t        -> XMLWC_
 * unsigned short -> XML16_
 * char           -> XML_
 * unsigned long  -> XML32_

To make these libraries work together in _one_ application I've
introduced a simple macro called XMLABI() which prefix all ABI
function with different tags as shown abow. See attached patch.

This patch is against the UTF32 support, but should not be to
hard to be modified to apply to original CVS HEAD.

If this patch is accepted we have to change the ABI version for
non char (XML_) libraries. They become incompatible with todays
applications which uses XML_ in UNICODE (libexpatw) environments.
We try to fix this now.

This patch also convert all XML_ function names to XMLABI() for
applications that did not change they names but defined XML_UNICODE.
This makes things easier for the developers. On the other hand we
get our change faster public.

Any comments are appreciated!

-- 
Raphael Bossek
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: utf32+sym.diff
Url: http://mail.libexpat.org/pipermail/expat-discuss/attachments/20051014/dbd970a5/utf32sym-0001.diff

From mmarathe at spikesource.com  Fri Oct 21 01:08:25 2005
From: mmarathe at spikesource.com (Manish Marathe)
Date: Thu, 20 Oct 2005 16:08:25 -0700
Subject: [Expat-discuss] expat tests
Message-ID: <1129849705.5108.90.camel@caledon.spikesource.com>

Hello All,

In the README filet, its written that if check, a unit test framework
for C is installed, complete unit regression tests would be executed.

Before installing check, I used to get 48 tests executed and passed
without any failures and after installing check there is no difference,
I am getting the same result. 

Any insights about how to use check to execute expat tests? I have
installed check in the default location /usr/local/bin..

Thanks much for your help!

-Manish


From kosic at iskratel.si  Fri Oct 21 11:55:55 2005
From: kosic at iskratel.si (Kosic Bojan    ITWEF2)
Date: Fri, 21 Oct 2005 11:55:55 +0200
Subject: [Expat-discuss] eccn code for expat parser
Message-ID: <142159FB6ED33A448373FBC8A76D850DAE0298@NTRD3.iskratel.si>

Hello,

does anyone know if expat parser have eccn (export control
classification number)?

Best regards,
Bojan

From johnnyturpin at gmail.com  Tue Oct 25 01:53:34 2005
From: johnnyturpin at gmail.com (johnny turpin)
Date: Mon, 24 Oct 2005 19:53:34 -0400
Subject: [Expat-discuss] Help cross-compiling expat
Message-ID: <4B3F155E-FA93-4F6D-8BB9-62616001700F@gmail.com>

I am not all that familiar with building libs in linux - I am trying  
to build expat for a different target system than the system I am  
building this on. It appears that I am suppose to use the configure -- 
host=HOST option, but I don't really know what to put for HOST. The  
top of my toolchain is /opt/hardhat - however all of the toolchain  
bins are at "/opt/hardhat/devkit/ppc/405/bin"

I am able to compile object files successfully, by simply redefining  
the CC variable as:

COMPILER = /opt/hardhat/devkit/ppc/405/bin/ppc_405-
PPC_INCLUDES = /opt/hardhat/devkit/ppc/405/target/usr/include

CC = $(COMPILER)gcc
CXX = $(COMPILER)g++
AR = $(COMPILER)ar
LD = $(COMPILER)ld


INCLUDES = -I$(srcdir)/lib -I$(PPC_INCLUDES) -I.

.....and so on


however, the linking seems to use the libtool defined by the LIBTOOL  
env variable, and ignores the "ld" definition above.


Any help here would be appreciated...






From zhu_dave at yahoo.com  Thu Oct 27 22:22:04 2005
From: zhu_dave at yahoo.com (Dave)
Date: Thu, 27 Oct 2005 13:22:04 -0700 (PDT)
Subject: [Expat-discuss] Compile Problem
Message-ID: <20051027202204.91702.qmail@web30610.mail.mud.yahoo.com>

Hello!

I just installed expat 1.95.8 on my Mac OS X 10.3.9,
but I couldn't compile one of my programs. I set the
DYLD_LIBRARY_PATH to /usr/local/lib. When I do the
following:

gcc -o myprogram myprogram.c -L /usr/local/lib/ -l
expat

It gives "ld: -L: directory name missing error". What
does this mean? What am I doing wrong? Is there any
documentation on this? Thank you.

regards.


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

From zhu_dave at yahoo.com  Fri Oct 28 00:46:35 2005
From: zhu_dave at yahoo.com (Dave)
Date: Thu, 27 Oct 2005 15:46:35 -0700 (PDT)
Subject: [Expat-discuss] parsing and string processing
Message-ID: <20051027224635.22016.qmail@web30612.mail.mud.yahoo.com>

Hello All,

I'm trying to profile a program which uses expat xml
parsing. What I'd like to see is where the xml parser
spends most of its time. So, my gprof results are as
follows:

  %   cumulative   self              self     total   
       
 time   seconds   seconds    calls  ms/call  ms/call 
name    
 50.0       0.01     0.01                            
_normal_getAtts [1]
 50.0       0.02     0.01                            
_normal_scanAtts [2]
   0.0       0.02     0.00        1     0.00     0.00 
_main [26]

I looked at the source code but couldn't understand
exactly what getAtts and scanAtts do. What I'm trying
to find out is if they do any sort of string/pattern
matching. Or maybe a general question, do xml parsers
do string/pattern matching a lot? If yes, how much
does it affect performance? Thank you for your help!

Regards,

Dave


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

From jeremy.kloth at fourthought.com  Fri Oct 28 01:09:02 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Thu, 27 Oct 2005 17:09:02 -0600
Subject: [Expat-discuss] parsing and string processing
In-Reply-To: <20051027224635.22016.qmail@web30612.mail.mud.yahoo.com>
References: <20051027224635.22016.qmail@web30612.mail.mud.yahoo.com>
Message-ID: <200510271709.02916.jeremy.kloth@fourthought.com>

On Thursday 27 October 2005 4:46 pm, Dave wrote:
> I looked at the source code but couldn't understand
> exactly what getAtts and scanAtts do. What I'm trying
> to find out is if they do any sort of string/pattern
> matching.

For the most part, they do *character* matching.  The XML specification 
defines the sets of characters that are allowed at any given point in a XML 
document.

> Or maybe a general question, do xml parsers 
> do string/pattern matching a lot?

Some parsers are implemented by using regular expressions (is that what you 
mean by "string/pattern matching"?).  Expat does basically the same thing, 
just unrolled in very optimized sub-functions for the respective 
non-terminals defined in the specification.

> If yes, how much does it affect performance?

It is basically a fact of life for any tokenizing lexer, be it a compiler, a 
XML parser, regular expression engine and what-not, the list is quite endless 
in the programming world.

> Thank you for your help! 

No problem, however I am curious as to the fascination with "string/pattern 
matching" as I seen basically this same message on the xml-sig list.

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From akumar at kodiaknetworks.com  Mon Oct 31 08:52:53 2005
From: akumar at kodiaknetworks.com (Ajit Kumar)
Date: Mon, 31 Oct 2005 13:22:53 +0530
Subject: [Expat-discuss] Parser sending only one charector
Message-ID: <000001c5ddf0$1a08a1b0$ac02a8c0@Ajit>

Hi,
I am using symbian- expat-1.95.8. While parsing an XML document the
parser sends only the first character of "TagName" to the "StartElement"
call back. Even the attribute seems to be not proper. I am using this
Expat on symbian platform. Is its all because of the Platform-symbian
issue?
I am waiting for the response.
Regards
ajit
 
 

From paul at toddsoftware.com  Mon Oct 31 11:11:40 2005
From: paul at toddsoftware.com (Paul Todd)
Date: Mon, 31 Oct 2005 10:11:40 -0000
Subject: [Expat-discuss] Parser sending only one charector
In-Reply-To: <000001c5ddf0$1a08a1b0$ac02a8c0@Ajit>
Message-ID: <000a01c5de03$7cb43460$4000a8c0@PaulsLaptop>

Are you using SyExpat or the C expat parser? 

-----Original Message-----
From: expat-discuss-bounces at libexpat.org
[mailto:expat-discuss-bounces at libexpat.org] On Behalf Of Ajit Kumar
Sent: 31 October 2005 07:53
To: Expat discussion
Subject: [Expat-discuss] Parser sending only one charector

Hi,
I am using symbian- expat-1.95.8. While parsing an XML document the parser
sends only the first character of "TagName" to the "StartElement"
call back. Even the attribute seems to be not proper. I am using this Expat
on symbian platform. Is its all because of the Platform-symbian issue?
I am waiting for the response.
Regards
ajit
 
 
_______________________________________________
Expat-discuss mailing list
Expat-discuss at libexpat.org
http://mail.libexpat.org/mailman/listinfo/expat-discuss



From michael_rudolf at t-online.de  Mon Oct 31 19:26:19 2005
From: michael_rudolf at t-online.de (Michael Rudolf)
Date: Mon, 31 Oct 2005 12:26:19 -0600
Subject: [Expat-discuss] Example on parsing character data
Message-ID: <436661CB.1040509@t-online.de>

Hey,
i am new to expat and i am searching for an example on how to parse 
character data that within a tag in the correct context. That means for 
now i would just like to print out the data inside the element handler.
Is there any tutorial or example on this?
Thanks!
Michael