Re: [Libxmlplusplus-general] parametrizing libxml++ for the character /string type

[murrayc t-online de (Murray Cumming)]

On Wed, 2003-01-29 at 17:35, Stefan Seefeld wrote:
> Murray Cumming wrote:
> 
> > Yes, but even in the unstable branch there's no point in applying major
> > stuff unless we know it's going to work completely.
> 
> right, but it's one thing to know where to head, and another to check in
> only stuff that completes a transition from the old to the new way of
> life. Anyways, I share your worries, and I think I can come up with a
> patch that doesn't leak (may be modulo some public methods that should
> at least be declared 'deprecated' for the time being).
> 
> > Actually, _I_ started to think that we might even get this into 1.0 if
> > it proves itself quickly enough.
> 
> ok.
> 
> >>Please let me know how you would like to proceed.
> > 
> > 
> > Well the patch as it stands seems to leak C++ wrapper instances. That
> > needs to be fixed - I like the idea of using the new libxml2
> > notification stuff to that.
> 
> good. I'm looking into that. libxml2 provides methods 
> xmlRegisterNodeDefault() and xmlDeRegisterNodeDefaults()

Do you have a URL for reference documentation?
 
> > What API changes are required?
> 
> As I said, for now we could just deprecate some methods, mostly
> constructors. That's just to prevent users from creating unbound nodes,

OK. Please just remove stuff - deprecation is useless if its broken and
we have no need for deprecation now anyway.

[snip]

> By the way, 'Attribute' should really derive from
> 'Node'.

Yes, maybe.

-- 
Murray Cumming
murray usa net
www.murrayc.com