Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23435 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16326 invoked by uid 1010); 15 May 2006 23:43:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16311 invoked from network); 15 May 2006 23:43:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2006 23:43:42 -0000 X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.5 (sometimes 2.4) (4) Received: from ([204.11.219.139:56381] helo=lerdorf.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 6B/CE-19568-D2219644 for ; Mon, 15 May 2006 19:43:42 -0400 Received: from [66.228.175.145] (borndress-lm.corp.yahoo.com [66.228.175.145]) (authenticated bits=0) by lerdorf.com (8.13.6/8.13.6/Debian-1) with ESMTP id k4FNhc4O028712; Mon, 15 May 2006 16:43:39 -0700 In-Reply-To: References: <003d01c672ef$6cde8370$0100a8c0@pc07653> <517361123ef66114064e2866c95e3caa@gravitonic.com> <000901c67857$c20fa190$0100a8c0@pc07653> <7abd987289270ef00178d1bbf8e32c0b@gravitonic.com> <002401c67866$d1497f50$0100a8c0@pc07653> <9c2e6ce480a09868788a4a4a46523235@gravitonic.com> <003a01c67869$160f52c0$0100a8c0@pc07653> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <6cd12210deaec9e6c1f753ec97c38177@gravitonic.com> Content-Transfer-Encoding: 7bit Cc: Nuno Lopes , PHPdev Date: Mon, 15 May 2006 16:43:18 -0700 To: Derick Rethans X-Mailer: Apple Mail (2.623) Subject: Re: [PHP-DEV] [php6] accepting an ascii string only From: andrei@gravitonic.com (Andrei Zmievski) Derick, The case we're talking about here is where a Unicode string containing only ASCII characters is passed to an extension, not a binary string with the same characters. -Andrei On May 15, 2006, at 2:53 PM, Derick Rethans wrote: > Yeah, but that doesnt mean you need to throw a hard error on passing a > unicode string here. They can also contain just ascii data which is > perfectly acceptable. > > > regards, > Derick