Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73079
Return-Path: <cryptocompress@googlemail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 33580 invoked from network); 12 Mar 2014 11:14:24 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Mar 2014 11:14:24 -0000
Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.214.43 as permitted sender)
X-PHP-List-Original-Sender: cryptocompress@googlemail.com
X-Host-Fingerprint: 209.85.214.43 mail-bk0-f43.google.com  
Received: from [209.85.214.43] ([209.85.214.43:65423] helo=mail-bk0-f43.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 09/03-17005-09140235 for <internals@lists.php.net>; Wed, 12 Mar 2014 06:14:24 -0500
Received: by mail-bk0-f43.google.com with SMTP id v15so1410186bkz.30
        for <internals@lists.php.net>; Wed, 12 Mar 2014 04:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=pAuSfzO0tpmfADA8r57ACH3o1T8AX2tVKg1Vm1xW8PE=;
        b=N/BDCP2mjz3AfEAhoj8Wsl2nogp+01B5JW6w49b8M/tCi9FpqZGjzsUfg3TFHPIP3E
         q4xjx59j9j9gr9C5Vi/MxBeY/apl05C54cxPpUvF7bSCP+lu77ME2/+NCDreMgp0J5mo
         yq+cykj/2L/06Aps8u30+nn/DeIGyQ49swJBDQq0SyJeRAGWW70nwn51QVGebT9FLKfi
         9VZAKDl6h0QNJXhnRNFSgZ6WWt+bhEQru7MshIn5CmQdNqVE28+9foCsr3Hf+pwmbyce
         TQLWGrMAdBdsL2RryghgUiyD9GyvSg7Aeoi+Qpj4JV4Fiavv2uRWxPzuf8kNKfuZnVFt
         A+Dg==
X-Received: by 10.205.12.199 with SMTP id pj7mr1466bkb.120.1394622861551;
        Wed, 12 Mar 2014 04:14:21 -0700 (PDT)
Received: from [192.168.1.115] (mnch-5d854468.pool.mediaWays.net. [93.133.68.104])
        by mx.google.com with ESMTPSA id zf3sm17996515bkb.4.2014.03.12.04.14.19
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 12 Mar 2014 04:14:20 -0700 (PDT)
Message-ID: <5320418A.4000600@googlemail.com>
Date: Wed, 12 Mar 2014 12:14:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Pierre Joye <pierre.php@gmail.com>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <531EE602.3090207@lsces.co.uk>	<531EEE2A.2000602@googlemail.com>	<531F0146.5010701@lsces.co.uk>	<53202DC5.4010306@googlemail.com>	<532033E1.60602@lsces.co.uk>	<53203687.7090405@googlemail.com>	<532037F4.6020204@googlemail.com> <CAEZPtU5G41OKb2FQF4ajKgszATqtwxL9E_k4Zc78RZGL8B4qnQ@mail.gmail.com>
In-Reply-To: <CAEZPtU5G41OKb2FQF4ajKgszATqtwxL9E_k4Zc78RZGL8B4qnQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Unicode strings?
From: cryptocompress@googlemail.com (Crypto Compress)

Am 12.03.2014 11:54, schrieb Pierre Joye:

> Also I do not get your argument earlier in this discussion saying that
> we should not implement objects or pseudo-objects for unicode support.
> where is the problem? It can work with existing functions as well,
> does not break BC, does not introduce weird syntax that prevents code
> from running in 5.x and 6.x (u"foo" will f.e.). The more I look at it,
> the more I think it is the way.

Am 06.03.2014 08:56, schrieb Crypto Compress:
> Would "type juggling" allow for autoboxing into a second string type 
> where needed (unicode-aware functions)? 

> No, we should not create an string-object to handle all intricacies of 
> unicode.
I'm against heavyweight objects not "object" per se.