Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78203 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44558 invoked from network); 21 Oct 2014 14:49:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2014 14:49:46 -0000 Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.220.49 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.220.49 mail-pa0-f49.google.com Received: from [209.85.220.49] ([209.85.220.49:59404] helo=mail-pa0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/D7-02077-68276445 for ; Tue, 21 Oct 2014 10:49:43 -0400 Received: by mail-pa0-f49.google.com with SMTP id hz1so1546237pad.36 for ; Tue, 21 Oct 2014 07:49:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=RRSiveLKoA1/Is5YnRKGK9DYGWP4hfr9lMEaEmjEYfU=; b=bAENcLua0+Z+teWaALibs2OrdI1l0/fe7lw3XP/bDHOKzko4Y/5gOkKbwE9KMqIgiN SAYPj9UtsF++k3aDoU63m5hS9E6W9/8dz9zNusXaCg6uM3WO//wonBi3YsP6FfiAuuep EMgHFd2vjiTZ897flPcz2F9uakHGN5tX5wR6f03HZnbxD6Fe/WfQUFr6U8/HFzhkENsC BI4ONg6WruQI2RwNXZXPlh7yY4UD/c6Yr/9WArP90e0egFhaUO/Tdg+3o8kBLQ7WeRlm 8SxXutPkFasmP8vH649LIydi7o63VhSX8fqX8IIOigUXuF5Yn4gbYs9175q2oWjtmdOw kNfg== X-Gm-Message-State: ALoCoQkBlkKTS+PY64fuWq05JsCieDsOl64mXaL+Ztgl03EGM5M1idznMZmLm9TCVqDUSNn4Wn/q X-Received: by 10.68.221.162 with SMTP id qf2mr4496720pbc.152.1413902979893; Tue, 21 Oct 2014 07:49:39 -0700 (PDT) Received: from [10.0.1.108] (c-71-198-113-183.hsd1.ca.comcast.net. [71.198.113.183]) by mx.google.com with ESMTPSA id i10sm12159815pdn.26.2014.10.21.07.49.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 07:49:39 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (11D201) In-Reply-To: <1413875212.2624.3.camel@localhost.localdomain> Date: Tue, 21 Oct 2014 07:49:40 -0700 Cc: "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <3DDBC023-07BB-498D-9398-B994B6548BC9@golemon.com> References: <1413875212.2624.3.camel@localhost.localdomain> To: Joe Watkins Subject: Re: [PHP-DEV] [RFC] UString From: php@golemon.com (Sara Golemon) > On Oct 21, 2014, at 0:06, Joe Watkins wrote: >=20 > Morning internalz, >=20 > https://wiki.php.net/rfc/ustring >=20 > 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. >=20 The backend abstraction seems overengineered to me. It could also lead to i= nconsistencies in behavior if ICU and Windows implement something in subtly d= ifferent ways. Since we're linking ICU for the rest of the intl extension anyway, it seems t= o me like we should just focus on it as an ICU wrapper. Also, I'd peopose a minor ammendment to this RFC that other intl classes be e= xtended to support taking UString instances as arguments (avoiding the impli= cit conversion to UTF8). That work doesn't have to gate adoption of the base= implementation, it'd just be useful to decide at the same time if we want t= o do so. -Sara=