Re: Replacing expat with libxml

From: Date: Sun, 27 Apr 2003 23:31:27 +0000
Subject: Re: Replacing expat with libxml
References: 1  Groups: php.internals php.xml.dev 
Request: Send a blank email to internals+get-1059@lists.php.net to get a copy of this message
On Sun, 2003-04-27 at 20:00, Rasmus Lerdorf wrote: > > 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! > Well, I won't give it the BC-safe stamp of approval, yet. It needs more testing. But, for example, PEAR and Pres2 work (install) without any modifications. My PHP & XML scripts (from my talk) work without modification. -Sterling > -Rasmus -- "Nothing is particularly hard if you divide it into small jobs." - Henry Ford

« previous php.internals (#1059) next »