Hi!
Even though I do agree that delaying the release every 2-3 months is bad, I believe this particular case deserves some special treatment.
Why? We have perfectly working parser now and no immediate need to replace it. I agree that new parser is faster and better, but we are perfectly capable to live without it for half a year until it's polished, if that proves to be the situation.
Releasing a half-working version just "because we have to have releases" is total nonsense.
Fully agreed here. That's why I'm against committing new parser without multibyte support.
So please instead of arguing with me, help Marcus and the others if you don't want the release postponed.
Unfortunately, I do not know Marcus' code and may not have resources to help him right now. Please keep in mind that while I am happy to help whenever I can, I am not under obligation to help on call to any project as soon as anybody wants me to, just because he wants it. That said, if somebody can and does fix new parser to support MB in reasonable time - I'm all for it.
Making new 5.x releases each year makes no sense to me, so 5.3 seems to be perfect candidate for the next several years if we want to implement something major.
What's wrong with making new 5.x releases each year if needed?
Right, and they want PHP to do its job and to do it good.
Having no mutibyte support used by a lot of people does not qualify as "do its job and to do it good". What qualifies is either 5.3 with old parser or 5.3 with new parser, fully compatible. As I believe I already explained about delaying release etc., I wouldn't repeat myself here.
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
