[boost] Re: xml library
I've just uploaded the preliminary version of my XML library to Yahoo files section as xml_library.zip. Comments are welcome. I think it's very nice, and I can already think of some code that could be made much clearer using this... ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[boost] Re: xml library
I've just uploaded the preliminary version of my XML library to Yahoo files section as xml_library.zip. Comments are welcome. Regards, Wojtek ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[boost] Re: xml library
On Sun, 17 Aug 2003 22:45:34 +0200, Wojtek Surowka wrote: I think that what is still missing in Boost is a library for reading and writing XML files. I have such a library, though in rather preliminary ... If there will be an interest, I can submit the library code and extend it. I am interested (I like the interface) and would like to test it. Cédric. ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[boost] Re: xml library
I'd be interested in such library. I think that boos::xml library should be using boost::spirit for parsing XML streams. I have now hand-coded parser. I'm actually more interested whether the interface of the library is ok, so I think I'll submit the current version, and I'll try to switch the implementation to spirit, if it fits there. Regards, Wojtek ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[boost] Re: xml library
I have been using expat for a while, and wrapping it in C++ classes. It's a very capable parser and supports lot's of stuff. My parser stuff is just done with a switch statement (since it's event driven), but it would be nice if you could use expat, but then register your element handlers to get called. This would be a cool design. I think it could get too complicated. The base difference between registered handlers design, and iterators design, is that in the former the parser has control, and in the latter the client code has control. I think that because of that fact it can be rather complicated to build iterator access based on handlers. But the other way around it is easy. I don't think I could actually use the iterator design that you have, since I need to handle the nesting of tags, so I need to know when I am started and finished a tag. I also need to know the normal CDATA or comments that just came through. Is this possible with the iterator idea? All of it is possible. CDATA support is available now. Comments are not supported yet. Nesting of tags is supported in the following way: if you have an iterator i, then ++i moves to the next thing on the same level. If i points to an element, then you can iterate through its contents with i-begin() and i-end(). I'll submit the library in short time, and you are very welcome to make experiments with it. Regards, Wojtek ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
