game to be doing so. We are in a feature freeze now so that we can get RC1 out of the door hopefully by the end of the month, and it just doesn't make sense to redesign the whole thing now.
Consider this: Judging from the comments on the list it seems to me that
a) people haven't really _used_ SimpleXML yet, just browsed through it.
b) people don't understand how it's supposed to work (e.g. disagreement about content of child nodes included or not)
c) it has internal problems (mentioned by Sterling)
So after all this ranting what I really think we should be discussing is if there are any *crucial* things which need changing or fixing without redesigning the whole thing.
As SimpleXML is sold as one of the major new features of PHP5 it worries me that we're about to publish a version (of the interface _and_ implementation) noone is really happy with. I can already see complaints coming about this and that where you'll have to say "but we can't change it anymore".
Maybe we need to take a step back and decide what's best for PHP5: A quick release (meaning either staying with the current SimpleXML way forever *or* de-bundling it for now) or a convincing SimpleXML (meaning a delay of RC1 and a feature defrost for it).
Choose wisely. (I don't know the answer but luckily I'm not the one to decide :-))
- Chris
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
