On Tue, Jul 04, 2006 at 01:02:35PM +0200, Buchcik, Kasimier wrote: > Hi, > > I learned from the sources that Result Tree Fragments, which > are stored in XPath objects are not freed anymore in the > XPath module itself but freed on Libxslt's side. > There are several comments in the code like: > "Freeing is not handled there anymore" > Therefore the @boolval field of an XPath object is set to 0, > after creation of such an object. > > Should we change xmlXPathNewValueTree() in order not to set > the @boolval field to 1? Setting it to 1 indicated that > xmlXPathFreeObject() should free the Result Tree Fragment > via xmlXPathFreeValueTree().
Hum, maybe this makes sense, but in that case the instructions should be given in that function description on how to get the RVT cleaned up properly in the XSLT context. And maybe add a warning that this must be used within XSLT only. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ [email protected] http://mail.gnome.org/mailman/listinfo/xslt
