Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25924 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90280 invoked by uid 1010); 4 Oct 2006 04:47:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 90265 invoked from network); 4 Oct 2006 04:47:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Oct 2006 04:47:11 -0000 Authentication-Results: pb1.pair.com header.from=pollita@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pollita@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 65.111.164.201 cause and error) X-PHP-List-Original-Sender: pollita@php.net X-Host-Fingerprint: 65.111.164.201 danica.alphaweb.net Linux 2.4/2.6 Received: from [65.111.164.201] ([65.111.164.201:41422] helo=danica.alphaweb.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4C/A0-22448-DCC33254 for ; Wed, 04 Oct 2006 00:47:10 -0400 Received: from talos.alphaweb.net ([69.12.155.129] helo=[172.31.5.147]) by danica.alphaweb.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1GUxjC-0005Xe-Rh; Tue, 03 Oct 2006 23:47:26 -0400 Message-ID: <45233CD9.3070307@php.net> Date: Tue, 03 Oct 2006 21:47:21 -0700 User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: andi@zend.com CC: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Per-request UG(unicode) From: pollita@php.net (Sara Golemon) andi@zend.com wrote: > What soup? Did you check out the patch? > It's actually not bad at all. It's even cleaner than what we had previously > as we just make sure we have two versions and we use the right one... > I did check it out. Even made changes to try out a few variations on the theme. I also stand by that I don't like the number of variables it throws into the mix. How about a compromise, we finish the code migration effort first, then address per-request semantics either before beta, or in the 6.1 branch. -Sara P.S. It feels a little weird that I'm cautioning you against unexpected side-effects this time (usually it's the other way around between us).