I know this is a great drawback of labVIEW but unfortunately these are
the tools I have to work with. Is there a work around (function or
combination of functions) I can use to get the next child (NodePtr)
form the childrenlist or should I defer to the xmlReader where the
callback function allows me to step through the document.

Perhaps there is a function that converts the current node of the
xmlReaderPtr to a xmlNodePtr?

Niels

On 9/26/07, Daniel Veillard <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 25, 2007 at 09:54:07PM +0200, Niels Van Hoef wrote:
> > Hi,
> >
> > I'm currently developing a new software application in labVIEW using
> > libXML to create new XML files. Implementing the "writer" went
> > smoothly but now I'm stuck at reading the XML back into memory from
> > file and stepping through it.
> >
> > Since I'm writing my code in labVIEW, I can only make some schematic
> > representation of which functions I'm calling and not past the actual
> > code.
> >
> > xmlParseFile (returns me a DocPtr)
> > xmlDocGetRootElement (returns me a NodePtr)
> >
> > At this point normal C code would look like this:
> >
> > cur = cur->xmlChildrenNode;
> >       while (cur != NULL) {
> >               ...
> >               ...
> >       }
> >
> > Unfortunately labVIEW doesn't allow me to do this, I can only do
> > functions calls. I'm kind of looking for a function "xmlGetNextChild"
> > (similar to xmlGetLastChild) or a work-around that I can implement in
> > labVIEW.
>
>   I don't know labVIEW, but that sounds a very serious bug in their bindings
> if they didn't provide this, you should ask them.
>
> 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

Reply via email to