Re: [RFC] UString

From: Date: Tue, 21 Oct 2014 08:01:55 +0000
Subject: Re: [RFC] UString
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-78178@lists.php.net to get a copy of this message
On Tue, 2014-10-21 at 08:40 +0100, Leigh wrote: > On 21 October 2014 08:06, Joe Watkins <pthreads@pthreads.org> 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

« previous php.internals (#78178) next »