Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6472
Return-Path: <moriyoshi@at.wakwak.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 44602 invoked by uid 1010); 15 Dec 2003 15:37:00 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 44549 invoked from network); 15 Dec 2003 15:36:59 -0000
Received: from unknown (HELO vckyb2.nw.wakwak.com) (211.9.230.145)
  by pb1.pair.com with SMTP; 15 Dec 2003 15:36:59 -0000
Received: from at.wakwak.com (at.wakwak.com [211.9.230.135])
	by vckyb2.nw.wakwak.com (Postfix) with ESMTP
	id 2393F401E9; Tue, 16 Dec 2003 00:36:58 +0900 (JST)
Received: from [192.168.0.130] (z58.220-213-31.ppp.wakwak.ne.jp [220.213.31.58])
	by at.wakwak.com (8.12.10/8.12.10/2003-09-30) with ESMTP/inet id hBFFavng014366;
	Tue, 16 Dec 2003 00:36:57 +0900 (JST)
	(envelope-from moriyoshi@at.wakwak.com)
In-Reply-To: <200312151032.28825.ilia@prohost.org>
References: <25BBBBC2-2CD2-11D8-8FCC-000A95CE0C62@at.wakwak.com> <200312131828.38053.ilia@prohost.org> <1071484672.1697.32.camel@kirin.dev.trd.p4pnet.net> <200312151032.28825.ilia@prohost.org>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <7E47960A-2F14-11D8-8F76-000A95CE0C62@at.wakwak.com>
Content-Transfer-Encoding: 7bit
Cc: "Stig S. Bakken" <Stig.Bakken@overture.com>,
	PHP Internals <internals@lists.php.net>
Date: Tue, 16 Dec 2003 00:36:47 +0900
To: ilia@prohost.org
X-Mailer: Apple Mail (2.606)
Subject: Re: [PHP-DEV] Re: Regarding the latest patch on fgetcsv() (stable branch)
From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi)

On 2003/12/16, at 0:32, Ilia Alshanetsky wrote:

> On December 15, 2003 05:37 am, Stig S. Bakken wrote:
>> So you think the right solution is to dismiss multibyte users and 
>> direct
>> them to the hacks (mbstring etc) that have been used previously 
>> instead
>> of thinking ahead?
>
> IMHO calling multibyte a hack would be great disservice to the 
> developers of
> that extension. We don't call ext/pgsql a hack, simply because it's not
> builtin, do we?

The extension is virtually a hack. Again, the developers of mbstring
had to choose the option, adding support for multiple encodings to PHP
by separating it as an extension, instead of integrating it into the
core implementation because we always ought to manage backwards
compatibilities.

>> If I were starting a language from scratch today, I would make 
>> character
>> encoding part of the string "zval" structure.  IMHO that's where it
>> belongs.  As an alternative for PHP 5[.1], there is room for a
>> "multibyte bit" in the zval that various functions can use to choose
>> between "sizeof(byte)==sizeof(char)" and "sizeof(byte) < sizeof(char)"
>> implementations.
>
> If you were designing a new language you wouldn't have legacy users 
> who'd
> suffer (significantly) because of features added for other users.

Well, the legacy users of PHP4 will significantly suffer for
PHP5's new features.

Moriyoshi