Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78178 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92913 invoked from network); 21 Oct 2014 08:02:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2014 08:02:05 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.212.175 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.212.175 mail-wi0-f175.google.com Received: from [209.85.212.175] ([209.85.212.175:45688] helo=mail-wi0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 09/71-19409-BF216445 for ; Tue, 21 Oct 2014 04:02:03 -0400 Received: by mail-wi0-f175.google.com with SMTP id d1so9240253wiv.8 for ; Tue, 21 Oct 2014 01:01:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; bh=JcU1TOWuCKNmLLcLrWPm75lIgUYDEdooir3LB6az3oE=; b=V9pZkM1LBHOESzj05JM7MrhCU+x9a68drf7o8b+kQzgeQ39UJY3h6IaNsuwMefFopo OZMRuMrkTlOEGOB3lEzdWp/WcEX/IpUg2EsVj7Hb+waukKWFdNpchS+q9IYCI9ft8hUK Do7S909R6WIG6B2kQNKSnWPanH8Q+ax+VQkKUgwCp0f5UcqjxfCtMLB+jdMv/pLoK/pp 4MRnrY3Zm2Fdx0nYDSd+c6sbIFR6YtIjfab/SWIv3XjbH5rJ7M+30fXpK4cAjp3YLpR0 AXJggLRiCTV4oGLAL87ymADMqGxWLVcDHO9ZvWozq9IbrFbg3m147bPJJOPb5GlSb7kT PqAQ== X-Gm-Message-State: ALoCoQk/pMBc1FFLHUKcKgOetU8UY6REuLrgM2iOKpY2ni0q2V3kjNYEf03LWz0uKZqyHv5VComK X-Received: by 10.194.173.10 with SMTP id bg10mr39885116wjc.16.1413878519523; Tue, 21 Oct 2014 01:01:59 -0700 (PDT) Received: from [192.168.1.67] ([86.159.154.179]) by mx.google.com with ESMTPSA id t10sm14476495wja.43.2014.10.21.01.01.58 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 21 Oct 2014 01:01:58 -0700 (PDT) Message-ID: <1413878515.2624.6.camel@localhost.localdomain> To: Leigh Cc: internals@lists.php.net Date: Tue, 21 Oct 2014 09:01:55 +0100 In-Reply-To: References: <1413875212.2624.3.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] UString From: pthreads@pthreads.org (Joe Watkins) On Tue, 2014-10-21 at 08:40 +0100, Leigh wrote: > On 21 October 2014 08:06, Joe Watkins wrote: > > Morning internalz, > > > > https://wiki.php.net/rfc/ustring > > > > This is the result of work done by a few of us, we won't be opening any > > vote in a fortnight. We have a long time before 7, there is no rush > > whatever. > > > > Now seems like a good time to start the conversation so we can hash out > > the details, or get on with other things ;) > > > > Breaks nothing, faster than mbstring, seems like win/win to me. > > > On the flip side, implementing UString as a scalar object would be inconsistent. At time of writing, array, int, float, bool, etc have no implementation available for this. > > I agree it shouldn't be a scalar object, but how about some operator > overloading like the GMP object has, so that you don't have to cast to > string for expected behaviour with type coercion etc. > > > Right now there are user-space libraries out there that cover a lot more functionality than UString. > > Do you need help implementing these? Do you think it would be > beneficial to briefly list which areas need attention on the RFC, so > they can be checked off over time? > > Overall +1 on the concept. Morning Leigh, ZEND_CONCAT is overloaded, as well as read_dimension and cast (to string) handlers. This seems to cover everything, unless I missed something ? Cheers Joe