Re: [xslt] Re: libxslt effects on _private member of libxml structures

[Daniel Veillard <veillard redhat com>]

On Fri, Mar 28, 2003 at 10:46:16AM +1100, Steve Ball wrote:
> Every suggestion so far would break binary compatibility
> and make the node slightly larger.  If we *don't* want either

  Yes, that's why for me it's spelled "libxml3" and work
on it will be posponed till "I or someone have time"

> BTW, a little while ago I sniffed through the Python interface
> code to see how it handles mapping libxml2 nodes to Python objects.
> As I recall, the interface does *not* attempt to maintain a
> backward pointer (from Python object to libxml2 node).

  Hum, the way around you mean. The python object points to the
C node but not the way around

> Every time a libxml2 node is referenced a new Python object
> is created.  Is that correct?

  yes,

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/