Marcin Kalicinski wrote:
It seems XML is even more complicated I thought it is, then ;-) If this is standard, it may be quite easy to implement includes in XML parser.
So, are you gonna roll namespace-aware XML parser? This is not trivial either, since there are things like default namespace and so on.
I was not aware that includes are connected with namespaces. I think my XML knowledge is not does not stand up to the need. I based my parser on Dan Nuffer's sources, and hope he got the corner cases right :-) On the other hand, if boost gets its XML library, my XML parser will be nothing more but obsolete, so it may not be worthwhile to spend too much time on it at the moment.
There are a number of applications that just needs a simple xml-parser. For example, most of the xml-files in my company are simple recursive structures with a single id="42" attribute here and there. But that id could easily be put into a tag instead. I have not yet understood why xml needs to be so sophisticated, and will probably continue to ignore all those wierd an advanced xml-features. Anyway, Marcin's parser also builds a ptree which is a great benefit compared to the DOM parsers I have seen. Just make sure it is well-defined what subset of xml that can be parsed and what cannot. In spirit of the library, anything that is not really easy and simple to support, should be rejected. -Thorsten