Hum, I didn't realized that the xmlNewTextWriter...() didn't use the set of usual I/O that libvirt exposes like for parsing etc ... Why don't you use xmlNewTextWriterFilename to save directly to the file ?
Daniel On Thu, Oct 09, 2014 at 02:39:29PM +0200, Peter Hofman wrote: > Well, when opening a TextWriter to memory, there is no clear way to write > it to disk. > Opening a new TextWriter to file taking a TestWriter to memory as parameter > might solve this. > But more solutions are possible. > Then you don't need xmlFileOpenW exported. > > Met vriendelijke groeten, > > Peter Hofman > Twitter <https://twitter.com/#!/pmhofman> / LinkedIn > <http://www.linkedin.com/in/knowmad> / Stackoverflow > <http://stackoverflow.com/users/1000917/peter> / Quora > <http://www.quora.com/peter-hofman> / Live > <https://profile.live.com/cid-62b51d236531b4d3/> > > > On 9 October 2014 13:31, Daniel Veillard <veill...@redhat.com> wrote: > > > On Wed, Oct 08, 2014 at 02:38:04PM +0200, Peter Hofman wrote: > > > Hi, > > > > > > Just wondering why xmlFileOpenW is not in the API XML document. > > > > > > Cheers, > > > > Because it's used for libxml2 I/O stack, and returns a void * which > > is a write context that the user whould not know how to use as > > this is platform specific... > > You think libxml2 doesn't export enough symbols ;-) ? > > > > Daniel > > > > -- > > Daniel Veillard | Open Source and Standards, Red Hat > > veill...@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ > > http://veillard.com/ | virtualization library http://libvirt.org/ > > -- Daniel Veillard | Open Source and Standards, Red Hat veill...@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/ _______________________________________________ xml mailing list, project page http://xmlsoft.org/ xml@gnome.org https://mail.gnome.org/mailman/listinfo/xml
