Re: Replacing expat with libxml

> The following incompatibilities exist: > > 1) some XML_ERROR_ * constants are irrelevant (they are stilled defined, > but they have no meaning for libxml). > 2) xml_error_get_string() just returns a blank string. This can be > changed in the next couple of days, i just need to implement error > strings ontop of libxml error codes. > > Having this library bundled internally will allow people to develop > other extensions which use libxml features, and will allow for future > extensions (for example, a fully compliant DOM extension) to easily be > added, without requiring extra bundling. > > Thoughts? I take it from this that old apps written against expat using the xml_set_element_handler() style will continue working? Like I said in New York, I agree we need to move to libxml, but I worry about breaking thousands of existing php-xml apps. If you have managed to make it BC-safe, perfect! -Rasmus