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. IMHO the best solution would be to leave (some) XML extensions enabled by default, however if libxml cannot be found or is unusable silently disable the affected extensions. Or perhaps give a warning indicating xml extensions are disabled at the end of configure. Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
