Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:34843 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43423 invoked by uid 1010); 21 Jan 2008 15:02:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 43407 invoked from network); 21 Jan 2008 15:02:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jan 2008 15:02:03 -0000 Authentication-Results: pb1.pair.com header.from=foolistbar@googlemail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=foolistbar@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 66.249.92.174 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: foolistbar@googlemail.com X-Host-Fingerprint: 66.249.92.174 ug-out-1314.google.com Received: from [66.249.92.174] ([66.249.92.174:53399] helo=ug-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5D/02-20131-9E3B4974 for ; Mon, 21 Jan 2008 10:02:02 -0500 Received: by ug-out-1314.google.com with SMTP id u40so865297ugc.29 for ; Mon, 21 Jan 2008 07:01:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=WcGm27XIfANgLMEM4JJH8zgEzfcGorQNWzHx6NYwmgQ=; b=StTdUvYHEBzYLXq/qZ1dleDWG0uioxZeVKiBQH/ChSv9yPo462YgGZCdAfVR56ymeCr6X6+FdE6mySBiwYlNEb+7ID9UzxYZPlGjdYzzlK+O6QaGHXD+JdHUL7TooQHWjH8IS4XqwVSCfO/crETCzYtGIcfkVlSZarMPM7q8igQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=TuwkbSvzvfqPVuciaChwpHibV+PCXubfjIkEmt7BFDtWvQXdFcoHwQ3eoIDbIK5RPNDfFwkwA/FZ7wmxo98ok3uaLJScKPgY0ErzEpjgMn0qP7hV+43OWehsrky20MYI3iw4ZdlutAftu3VNypp3FgA9JDQgGQstvIWAVVCnQdg= Received: by 10.78.142.14 with SMTP id p14mr9134913hud.75.1200927716600; Mon, 21 Jan 2008 07:01:56 -0800 (PST) Received: from ?192.168.0.116? ( [86.151.228.75]) by mx.google.com with ESMTPS id t12sm6571106gvd.2.2008.01.21.07.01.54 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Jan 2008 07:01:55 -0800 (PST) Cc: php-dev Message-ID: To: Antony Dovgal In-Reply-To: <4794AE48.20005@daylessday.org> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v915) Date: Mon, 21 Jan 2008 15:01:52 +0000 References: <4794AE48.20005@daylessday.org> X-Mailer: Apple Mail (2.915) Subject: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP From: foolistbar@googlemail.com (Geoffrey Sneddon) On 21 Jan 2008, at 14:38, Antony Dovgal wrote: > 2) it's supposed to mean compatibility, but can be changed only in =20 > php.ini, which > means users would still have to maintain 2 versions of their software: > one for On and second for Off. I think this is the biggest issue for anyone writing software is the =20 fact that is can only be changed in php.ini =97 it may well be fine if =20= it can be set on a per request basis (though there will still be =20 issues with that (software libraries that have to cope with both types =20= of request, for example)). > 3) 2+ bigger codebase [1] (with lots of duplicates because we have =20 > to do > same things in native and unicode modes); =46rom the cross-reference I assume you mean PHP's codebase. We still =20= need binary string support =97 Unicode is only suitable for textual =20 content. Images, for example, are binary data and we still need binary =20= strings for them. Not everything people deal with in PHP is a textual =20= string. -- Geoffrey Sneddon