Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6674
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <200312221128.hBMBS6ng038960@at.wakwak.com>
Date: Mon, 22 Dec 2003 20:30:37 +0900
MIME-Version: 1.0
To: Christian Schneider <cschneid@cschneid.com>
Cc: ilia@prohost.org, PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In-Reply-To: <3FE6C171.7@cschneid.com>
References: <200312211312.52512.ilia@prohost.org>
	<08A4825B-340D-11D8-B114-000A95CE0C62@at.wakwak.com>
	<3FE6C171.7@cschneid.com>
Subject: Re: [PHP-DEV] fgetcsv() conclusion
From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi)

Christian Schneider <cschneid@cschneid.com> wrote:

> Moriyoshi Koizumi wrote:
> >> 1) Leave things they way they are now, giving everyone a partial 
> >> support for
> >> multibyte string in fgetcsv() and 2-3 performance decrease in all 
> >> instances.
> > 
> > Of course this is my choice.
> 
> I'm not sure this is what you want because the words "_partial_ support" 
> seem to be the catch here. I guess Ilia argues that the current way is 
> broken.

What Ilia is mentioning as "partial support" is that the current 
implementation can not handle multibyte delimiters and enclosures,
which I don't find necessary. I've never encountered a real situation 
that requires multibyte delimiters or enclosures. Did you read through
the entire thread..?

Moriyoshi