libxmlplusplus-general — Open discusions about libXML++

[libxml++] [patch] Namespace class and custom_dom example

[Dan D. <da...@de...>]

Moderators, please discard the previous message sent using the wrong
>From address.
----
Hi guys,

I implemented XML Namespaces support against the current CVS. I also
made an example custom_dom that demonstrates deriving classes from
Element and using a SAX parser to build a tree of these derived objects
to make it easy to serialize and deserialize a custom DOM. This example
also tests the Namespace.

There are overloaded methods that can take a Namespace object as a
parameter, but I have not tested these. The example, just uses the
methods with prefix or prefix/uri parameters. I imagine the methods that
take a Namespace object might be useful with DOM manipulations. For now,
I wanted to get some implementation feedback for a merge to ease ongoing
development.

I am using this as the basis for a rewrite of the Kino video editor that
uses the W3C SMIL2 for its project file format. We need namespaces
support because we will have Kino specific features in it and only
implement selective SMIL modules while doing other modules a different
way. I will also look at Bakery soon to get ideas about how it
approaches the Document_XML.

+-DRD-+

Re: [libxml++] problem in compiling basic C++ with libxml++ library

[Jan T. <tus...@ya...>]

Hi,

to me it looks like the usual g++ version mess.

Since g++ linker > 2.95 changed mangling etc. the linker doesn't find the 
symbols.

Make sure you compile the program with the right compiler / linker.

My guess: your libxml++ is not compatible with your system.

Cheers, Jan

[libxml++] problem in compiling basic C++ with libxml++ library

[Fabrizio L. <Fab...@Au...>]

 Hello,

I apologize for the very basic problem but I am just at the beginning with
C++.
I am trying to use the libxml++ library and I thought to have a look at the
examples. I have downloaded and installed the debian packages available on
http://mirror.raw.no/gnome2.2/, then I have written a very simple source
like this:

#include <libxml++/libxml++.h>

int main(int argc, char *argv[])
{
return 0;
}

I compile it with g++ -Wall -o xml xml.cc `pkg-config --libs --cflags
libxml++-1.0` and i get a lot of errors while linking:

/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_rethrow'
/usr/lib/libxml++-0.1.so: undefined reference to `std::uncaught_exception()'
/usr/lib/libxml++-0.1.so: undefined reference to `std::exception::~exception
[not-in-charge]()'
/usr/lib/libxml++-0.1.so: undefined reference to
`std::__throw_ios_failure(char
const*)'
/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_call_unexpected'
/usr/lib/libxml++-0.1.so: undefined reference to `std::__throw_bad_alloc()'
/usr/lib/libxml++-0.1.so: undefined reference to `vtable for
__cxxabiv1::__si_class_type_info'
/usr/lib/libxml++-0.1.so: undefined reference to `operator delete(void*)'
/usr/lib/libxml++-0.1.so: undefined reference to
`std::__throw_length_error(char
const*)'
/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_end_catch'
/usr/lib/libxml++-0.1.so: undefined reference to `__gxx_personality_v0'
/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_pure_virtual'
/usr/lib/libxml++-0.1.so: undefined reference to
`std::ios_base::Init::Init[in-charge]()'
/usr/lib/libxml++-0.1.so: undefined reference to `vtable for
__cxxabiv1::__class_type_info'
/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_throw'
/usr/lib/libxml++-0.1.so: undefined reference to `vtable for
__cxxabiv1::__vmi_class_type_info'
/usr/lib/libxml++-0.1.so: undefined reference to `std::ios_base::Init::~Init
[in-charge]()'
/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_begin_catch'
/usr/lib/libxml++-0.1.so: undefined reference to `__cxa_allocate_exception'
/usr/lib/libxml++-0.1.so: undefined reference to `operator new(unsigned)'
collect2: ld returned 1 exit status

Could you please help me to realize where is the mistake? I am wondering
that I
get so many errors from a simple source like this and I don't know exactly
if it
is my fault or maybe the debian packager did something wrong in putting the
right dynamic library (I see /usr/lib/libxml++-0.1.so, so version 0.1).
Thanks
in advance for your help.

Fabrizio

Re: [libxml++] msvc project files

[Christophe de V. <cde...@al...>]

Thanks !

Le Dimanche 20 Juillet 2003 12:00, Ephraim Vider a =E9crit :
> Done.
>
> added new project and updated workspace.
>
> -eff
>
> ----- Original Message -----
> From: "Christophe de Vienne" <cde...@al...>
> To: <lib...@li...>
> Sent: Friday, July 18, 2003 11:46 PM
> Subject: [libxml++] msvc project files
>
> > Hi,
> >
> > Just after making the release I realise that the msvc project file hasn=
't
>
> been
>
> > updated to include the new example (import_node).
> >
> > Ephraim, could you update it as soon as you can so we don't forget it f=
or
>
> next
>
> > release :-/ Thanks very much.
> >
> >
> > Cheers,
> >
> > Christophe
>
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> Libxmlplusplus-general mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general

Re: [libxml++] msvc project files

[Ephraim V. <ef...@ep...>]

Done.

added new project and updated workspace.

-eff

----- Original Message ----- 
From: "Christophe de Vienne" <cde...@al...>
To: <lib...@li...>
Sent: Friday, July 18, 2003 11:46 PM
Subject: [libxml++] msvc project files


> Hi,
>
> Just after making the release I realise that the msvc project file hasn't
been
> updated to include the new example (import_node).
>
> Ephraim, could you update it as soon as you can so we don't forget it for
next
> release :-/ Thanks very much.
>
>
> Cheers,
>
> Christophe
>

[libxml++] msvc project files

[Christophe de V. <cde...@al...>]

Hi,

Just after making the release I realise that the msvc project file hasn't been 
updated to include the new example (import_node).

Ephraim, could you update it as soon as you can so we don't forget it for next 
release :-/ Thanks very much.


Cheers,

Christophe

Re: [libxml++] 0.25 soon.

[Eric B. <er...@co...>]

> I see. In fact this is what I would call the old method. With pkg-config, this 
> is already supported. All you have to do is :
> 
> PKG_CHECK_MODULES(XMLPP, libxml++-1.0 >= 0.25.0)

Ok. Missed that. The patch I submitted still won't hurt though. I doubt
it will encourage anyone to use the old method who is currently using
pkg-config; it simply adds an argument which always should have been
there.

If we really want people to use pkg-config, then we should remove
libxml++.m4 from the distribution altogether so that older-style
autoconfers like me will notice the change :)

Cheers,

Eric

Re: [libxml++] 0.25 soon.

[Christophe de V. <cde...@al...>]

Le Mardi 15 Juillet 2003 22:07, Eric Bourque a =E9crit :
> On Tue, 2003-07-15 at 15:49, Christophe de Vienne wrote:
> > Checking version of what ?
>
> The installed version of the library. See the comments in the patch I
> just submitted.
>

I see. In fact this is what I would call the old method. With pkg-config, t=
his=20
is already supported. All you have to do is :

PKG_CHECK_MODULES(XMLPP, libxml++-1.0 >=3D 0.25.0)

Moreover this wil define some extra variables, XML_LIBS and XML_CFLAGS.
I think we should encourage this method.

(BTW we should switch to this to detect libxml.)

Will this macro encourage the old fashion method ? I'm not sure. Murray wha=
t=20
do you think about it ?


Best regards,

Christophe

Re: [libxml++] 0.25 soon.

[Eric B. <er...@co...>]

On Tue, 2003-07-15 at 15:49, Christophe de Vienne wrote:
> Checking version of what ?

The installed version of the library. See the comments in the patch I
just submitted.

Cheers,

Eric

[libxml++] [ libxmlplusplus-Patches-771848 ] added version checking to autoconf macro

[SourceForge.net <no...@so...>]

Patches item #771848, was opened at 2003-07-15 16:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=312999&aid=771848&group_id=12999

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric Bourque (shaderman)
Assigned to: Nobody/Anonymous (nobody)
Summary: added version checking to autoconf macro

Initial Comment:
This patch adds version checking to the autoconf macro
so that you can have something like:

AM_LIBXMLPP(0.25.0)

in your configure.in should you need a feature which is
present only from 0.25.0 on (like import_node).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=312999&aid=771848&group_id=12999

Re: [libxml++] 0.25 soon.

[Christophe de V. <cde...@al...>]

Le Mardi 15 Juillet 2003 20:48, Eric Bourque a =E9crit :
> On Tue, 2003-07-15 at 12:57, Christophe de VIENNE wrote:
> > If you notice anything that should be fixed before, please signal on the
> > mailing-list.
>
> It would be nice if the autoconf macro did version checking ... I'll see
> if I can add that and send you a patch soon.
>

Checking version of what ?

Re: [libxml++] 0.25 soon.

[Eric B. <er...@co...>]

On Tue, 2003-07-15 at 12:57, Christophe de VIENNE wrote:
> If you notice anything that should be fixed before, please signal on the 
> mailing-list.

It would be nice if the autoconf macro did version checking ... I'll see
if I can add that and send you a patch soon.

Cheers,

Eric

[libxml++] 0.25 soon.

[Christophe de V. <cde...@al...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I'd like to release libxml++ 0.25 this week.

If you notice anything that should be fixed before, please signal on the=20
mailing-list.

Best regards,

Christophe
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/FDJuB+sU3TyOQjARAsQXAKCN44SRa3Y0/E2+9+Z3ItQYyp3BZgCeM2cc
z54USm2sl/v/bspXeoXVdNE=3D
=3D/Yjf
=2D----END PGP SIGNATURE-----

Re: [libxml++] using throw() in function declaration

[Christophe de V. <cde...@al...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Mardi 15 Juillet 2003 18:38, Christophe de VIENNE a =E9crit :
>
> Ok, so let's move on. This should be commited in a few hours.
>

It's in.

=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/FDIHB+sU3TyOQjARAqT7AJ9R0PRuor+XM6B3C25uD+dIRvsQgACdEyhR
H1L+wvZKDckRFJAjAZJhMGg=3D
=3D4bmT
=2D----END PGP SIGNATURE-----

[libxml++] using throw() in function declaration

[Christophe de V. <cde...@al...>]

Hi all,

While discussing about his patch with Eric, we remarked that some functions in 
libxml++ declare which exceptions may be raised (in Document for example), 
and some others not.
I consider that this is inconsistent. Either we do it for all of them, either 
not at all.
In my opinion we shouldn't do it. Before correcting it this way I'd like to 
have some other opinions.

Please tell me if you think we should :

1. Do not use throw in function declaration
or
2. Use it.

Thanks,


Christophe

Re: [libxml++] importing nodes from one doc to another

[Eric B. <er...@co...>]

On Wed, 2003-07-09 at 16:35, Christophe de Vienne wrote:
> Feel free to propose a patch.

I just uploaded one to the patch manager. It's against 0.24 since I was
writing it on the train and didn't have connectivity to get the cvs
version :(

Cheers,

Eric

[libxml++] [ libxmlplusplus-Patches-769830 ] import_node patch

[SourceForge.net <no...@so...>]

Patches item #769830, was opened at 2003-07-11 15:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=312999&aid=769830&group_id=12999

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric Bourque (shaderman)
Assigned to: Nobody/Anonymous (nobody)
Summary: import_node patch

Initial Comment:
This patch adds an import_node member funtion to the
Node class to allow one to copy nodes from another
document into the current document.

The patch also includes a small example of using the
new method.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=312999&aid=769830&group_id=12999

Re: [libxml++] importing nodes from one doc to another

[Eric B. <er...@co...>]

On Wed, 2003-07-09 at 16:35, Christophe de Vienne wrote:
> Hi Eric,
>=20
> Le Mercredi 9 Juillet 2003 22:31, Eric Bourque a =E9crit :
> > Is there any way in libxml++ to import nodes from one document to
> > another similar to xmlDocCopyNode() followed by making it a child=
 of a
> > node in libxml2? The current API suggests not. Perhaps I will loo=
k into
> > adding it since I need this functionality.
>=20
> There is indeed not such a feature.
> But it would be very welcome, since I think it will not change the =
existing=20
> API, but just add a few functions.
>=20
> Feel free to propose a patch.

Ok - I will look into this.

Cheers,

Eric

Re: [libxml++] importing nodes from one doc to another

[Christophe de V. <cde...@al...>]

Hi Eric,

Le Mercredi 9 Juillet 2003 22:31, Eric Bourque a =E9crit :
> Is there any way in libxml++ to import nodes from one document to
> another similar to xmlDocCopyNode() followed by making it a child of a
> node in libxml2? The current API suggests not. Perhaps I will look into
> adding it since I need this functionality.

There is indeed not such a feature.
But it would be very welcome, since I think it will not change the existing=
=20
API, but just add a few functions.

=46eel free to propose a patch.

Cheers,

Christophe

[libxml++] importing nodes from one doc to another

[Eric B. <er...@co...>]

Is there any way in libxml++ to import nodes from one document to
another similar to xmlDocCopyNode() followed by making it a child of a
node in libxml2? The current API suggests not. Perhaps I will look into
adding it since I need this functionality.

Cheers,

Eric

Re: [libxml++] DomParser crashes on empty file

[Christophe de V. <cde...@al...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Lundi 7 Juillet 2003 18:10, Thomas Jarosch a =E9crit :
> Christophe,
>
> > Hi,
> >
> > It is indeed a bug, which has been fixed in libxml 0.24.0.
>
> That reminds me that freshmeat still got 0.23.0 as current version.
> I remember you wanted to announce it, but something wasn't working...
>

yep. I've redone it one hour ago. Hope it will work this time...

Cheers,

Christophe
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/CasHB+sU3TyOQjARAosLAJkBRpuc7oyPI4HjSan+vPwEV9ZmSwCeKhn4
=46vJo4HDhcLiLR85PhDMs/4k=3D
=3DI+qo
=2D----END PGP SIGNATURE-----

Re: [libxml++] DomParser crashes on empty file

[Jan T. <tus...@ya...>]

On Montag, 7. Juli 2003 18:05, Christophe de VIENNE wrote:
> Le Lundi 7 Juillet 2003 17:58, Jan Tusch a écrit :
> > libxml2-version : 2.5.7
> > libxml++-version : 0.23.0
> >
> >
> > If that is not a bug, what's the reason for this weird behavior ?
>
> Hi,
>
> It is indeed a bug, which has been fixed in libxml 0.24.0.
>
> Best regards,
>
> Christophe
>
>

Sorry for razzing you with fixed bugs.

Jan

>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Libxmlplusplus-general mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general

Re: [libxml++] DomParser crashes on empty file

[Thomas J. <tho...@in...>]

Christophe,

> Hi,
>
> It is indeed a bug, which has been fixed in libxml 0.24.0.

That reminds me that freshmeat still got 0.23.0 as current version.
I remember you wanted to announce it, but something wasn't working...

Thomas

Re: [libxml++] DomParser crashes on empty file

[Christophe de V. <cde...@al...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Lundi 7 Juillet 2003 17:58, Jan Tusch a =E9crit :
> libxml2-version : 2.5.7
> libxml++-version : 0.23.0
>
>
> If that is not a bug, what's the reason for this weird behavior ?

Hi,

It is indeed a bug, which has been fixed in libxml 0.24.0.

Best regards,

Christophe
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/CZpLB+sU3TyOQjARAgohAJ9rvu5qBu0eDogt7ErcLOwnpr2qoQCgyXKj
ChJzTX//CdnhOXWk1L7s04Q=3D
=3Dkz4x
=2D----END PGP SIGNATURE-----

[libxml++] DomParser crashes on empty file

[Jan T. <tus...@ya...>]

Hi folks,

The DomParser appears to have problems with empty files, i.e. there has 
to be at least one character available, otherwise it is producing SEGFAULT
in xmlpp::Document constructor (doc==NULL) ... 
according to the output of gdb when debugging the following program :


int main(int argc, char** argv)
{
   if(argc != 2)
     return 1;
   xmlpp::DomParser P;
   try {
     P.parse_file(argv[1]);
   }
   catch(const xmlpp::exception& e) {
      cerr << "libxml++ exception : " << e.what() << endl;
   }
   return 0;
}


gdb .....
+++++++++++++++++++++++++++++++++++++++++++++
GNU gdb 2003-06-06-cvs-debian
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...
(gdb) set args /tmp/emptyFile
(gdb) run
Starting program: /home/tmp/test /tmp/emptyFile
[New Thread 16384 (LWP 3427)]
/tmp/emptyFile:1: error: Document is empty

^
/tmp/emptyFile:1: error: Start tag expected, '<' not found

^

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 3427)]
Document (this=0x80f27c0, doc=0x0) at document.cc:177
177     document.cc: Datei oder Verzeichnis nicht gefunden.
        in document.cc
(gdb) where
#0  Document (this=0x80f27c0, doc=0x0) at document.cc:177
#1  0x4021d62a in xmlpp::DomParser::parse_context() (this=0xbffff830) at domparser.cc:87
#2  0x4021d40e in xmlpp::DomParser::parse_file(std::string const&) (this=0xbffff830, filename=@0xbffff820) at domparser.cc:58
#3  0x0804ab25 in main (argc=2, argv=0xbffff8b4) at test.cpp:50

+++++++++++++++++++++++++++

libxml2-version : 2.5.7
libxml++-version : 0.23.0


If that is not a bug, what's the reason for this weird behavior ?

Regards, Jan