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),
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 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. 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.
Andi
At 07:42 AM 9/15/2005, Jani Taskinen wrote:
Touché. :)
But I must insist. I want to upgrade at some point.
I might even have use for unicode, at some point. But why can't
I disable it as long as it does not give me anything I need?
On other topic, I want to do the spring cleaning we discussed earlier
already in PHP 5.2. Not the most dramatic ones but the ones everyone
agrees on. Like removing the register_globals..etc.
Or is the only solution to fork?
--Jani
On Thu, 15 Sep 2005, Wez Furlong wrote:
No one is forcing you to upgrade to PHP 6.
--Wez.
On 9/15/05, Jani Taskinen <[EMAIL PROTECTED]> wrote:
I don't care about this as long as I can DISABLE it from
my PHP builds (and not be forced to link it with ICU).
--Jani
On Wed, 14 Sep 2005, Rasmus Lerdorf wrote:
Makoto Tozawa wrote:
Jani Taskinen wrote:
Show me one such person please. One that does this using PHP. :)
One that really NEEDS this to be possible..
It's impossible to find one as PHP doesn't support it today.
Think of defining a class which encapsulates a database table, and the
table name and column names are in native languages. If PHP restricts
the class and function names to ascii characters, programmers need to
maintain the mapping from the table name to the class name, and the
column name to the set/get function name. Can you guess how painfull
it would be?
Think of a code generator which generates classes from database tables.
What kind of class/function names the code generator could automatically
generate if the programming language restricts the identifiers to ascii
characters?
Same goes for SOAP, COM and Java integration. All of these potentially
need to map to unicode identifiers and trying to work around this would
be annoying.
-Rasmus
--
Donate @ http://pecl.php.net/wishlist.php/sniper
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
Donate @ <http://pecl.php.net/wishlist.php/sniper>
Disclaimer: Donating money may make me happier
and friendlier for a limited period!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
