To quote from PEAR/Common.php's infoFromString() method (used to parse package.xml, and the base of all installation methods)
$xp = @xml_parser_create();
if (!$xp) {
return $this->raiseError('Unable to create XML parser');
}Regards, Greg
Rasmus Lerdorf wrote:
On Fri, 24 Oct 2003, Greg Beaver wrote:
Ilia Alshanetsky wrote:
One solution which was to bundle libxml with PHP got rejected and if my recollection is correct you agreed with that decision. IMHO that was a good decision, bundling a huge library (3.2+ megs as of 2.6.0) almost as big as PHP itself seems kind of strange.
Reverting back to expat does not appear like a valid option as that prevents a common backend for all of the xml extensions. Although if someone can come up with a good solution, maybe fall back to expat if no operational libxml is found?
Given xml's perceived popularity disabling XML is not an option, that and I believe (not 100% sure) it would cause problems for PEAR.
I can verify this. PEAR is structured around the ability to parse a package.xml using expat-style parsing. Without xml, there is no PEAR.
That's a bit misleading. Without XML the pear installer just runs slower since it uses a user-space xml parser.
-Rasmus
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
