I think most of that list can be implemented but while it's easy to
give a +1 and make the changes, I still want to dive into some of
them more. I've been much busier looking at the Unicode stuff and
5.1.x patches so I didn't have a lot of time to look into it. I think
it's quite reasonable to do that. Don't worry, I won't linger like
you did with some of your promised patches :) (Just kidding).
I doubt you are looking to use PHP 6 in production in the near future...
Andi
At 04:46 PM 9/15/2005, Pierre Joye wrote:
On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Jani,
>
> I don't really see how PHP 6 can support a build
> without ICU. With the whole core using the ICU
> library it's almost like not supporting libC. If
> you find a way I'd be happy to hear about it and
> discuss but I think it's not realistic.
>
> Regarding spring cleaning, I suggest to relax a
> bit. I don't think it should be done before PHP 6
> (nor did others including Rasmus suggest that),
I think it was ironic, but why do we not do that now in HEAD?
> and I am still trying to work through that list
> and trying to understand where it makes
> sense/doesn't make sense to break things. I
The Rasmus list has been wastly approved. I fail to see why we should
not apply some request of this list.
> do think we have to be careful about some of that
> stuff, and as PHP 6 won't be released next month,
> and most of those "spring cleaning" patches are
> trivial, I don't see a reason to hurry up and not
> give some more time.
The past prooved to me that delaying changes is not a good idea.
Changes _never_ come.
> Nothing is gained by doing
> it today, and I'm sure Andrei would be happy to
> get help from the dev guys on migrating functions
> to Unicode which is a lot more work and on the critical path to PHP 6.
Having a code base cleaned could help to convert to migrate ;)
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
