Re: [Libxmlplusplus-general] new release please
- From: Christophe de Vienne <cdevienne alphacent com>
- To: libxmlplusplus-general lists sourceforge net
- Subject: Re: [Libxmlplusplus-general] new release please
- Date: Mon, 9 Dec 2002 20:56:26 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Lundi 9 Décembre 2002 20:12, Murray Cumming wrote:
> On Mon, 2002-12-09 at 20:17, Christophe de Vienne wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Lundi 9 Décembre 2002 19:46, Murray Cumming wrote:
> > > Could we have a new release please?
> >
> > As soon as I do those node type stuffs, or at least correct the problems
> > present when loading and saving a single file (which is, in my opinion, a
> > blocking bug), yes.
> >
> > I plan to do this by the end of the week.
>
> You mean the content nodes? I was just about to ask you to wait until
> we've fixed that.
yes. And the comment nodes at the same time.
I'm thinking of doing a base Node class, from which will herit ElementNode,
CommentNode, TextNode, and the 4 other possible node types.
For the get_content and set_content accessors, I have 2 alternatives :
- put them in the Node base class, and implement it differently in TextNode /
CommentNode (here the meaning is obvious) and in ElementNode (here they would
set/get the content of a child TextNode, and eventually create one if it
doesn't exists). It is the behavior of libxml (see xmlNodeSetContent
implementation in tree.c).
- put them only in TextNode and CommentNode.
The first one give the possibility to manipulate Nodes with content without
having to know about the TextNodes in a basic utilisation.
The second one avoid the possible mistakes because of mixing the different
accessor behavior...
A third one would be to do the second one, plus adding another accessor on
ElementNode with a different name. But which one ?
I think I prefer the first solution, with a good documentation. For now...
I'm going to have a closer look to Xerces before making a decision.
Any comment/advise is welcome !
> I noticed that get_content() doesn't seem to work.
? well in the current CVS version, the dom_parser example shows me some
contents. What did you mean exactly ?
Christophe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE99PVqB+sU3TyOQjARApAKAJwMW58+qs4GRs0L2XfZsoeA1tbIFgCgwp/P
XNd85chsOOn3H9n0OnGEOxw=
=3qaW
-----END PGP SIGNATURE-----
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]