On Sat, May 05, 2007 at 03:16:54PM +0200, Joachim Zobel wrote: > Am Samstag, den 05.05.2007, 07:06 -0400 schrieb Rob Richards: > > - Try not to use globals. Many functions have been added over the years > > that allow settings/options to be passed directly eliminating the need > > to use globals. > > I would prefer not to use globals. The problem I have to deal with is > that my module calls the SAX2 callbacks (from SAX2.c). These callbacks > assume the memory that is passed to them has been allocated by libxml2, if you're calling the callbacks from libxml2 just to build a tree it's bad, either use one of the parsers or build the tree with the tree API. Other uses are not suported, in the sense that I may break randomly how the callback works. I don't know why you are doing this but this sounds extremely fishy, would you care to explain, because I'm trying to guess and mostly I see only bad reasons.
Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ xml mailing list, project page http://xmlsoft.org/ [email protected] http://mail.gnome.org/mailman/listinfo/xml
