Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60706 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71306 invoked from network); 1 Jun 2012 08:02:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2012 08:02:58 -0000 Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.217.170 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.217.170 mail-lb0-f170.google.com Received: from [209.85.217.170] ([209.85.217.170:48345] helo=mail-lb0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D0/76-45898-13778CF4 for ; Fri, 01 Jun 2012 04:02:58 -0400 Received: by lbgc1 with SMTP id c1so1604129lbg.29 for ; Fri, 01 Jun 2012 01:02:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=19K8AAmOTk6FXatATSJZ/3/tjd75IHKgE8qlahUIqpk=; b=iDyyrxcJEM0HLVEzzMuOdnlvt2WL18gC6dQvwo5++E+HNLNTyA11U/DHTiUgUkfAk6 AnaCGksbu2ZLo1g+38EJ+6KzTqXb1AUKd/AOcQ3jACZbh4rDX8q39y5ZmQwsLlwSJN03 lf3DxgtQ6MP1zJPo2aIkhxWA/7JcuNDDGBFll/oPuFWmROEOgzvMYyoTk1VO1NEjXt1Z trthmzLKJr6IDNoLTPDMrQYH0SjGeJHf3l/DLxDk84Aat13am1OvbAeRaVsRJaKNR7ha vfLe9xwybFI3oels/w9GZ2SrubHTGwQDYT2bkCXb1jPaxcYKrg7bn0kkYm/QIi3ctdDh Jkcw== MIME-Version: 1.0 Received: by 10.112.86.166 with SMTP id q6mr1424450lbz.6.1338537773841; Fri, 01 Jun 2012 01:02:53 -0700 (PDT) Received: by 10.112.98.131 with HTTP; Fri, 1 Jun 2012 01:02:53 -0700 (PDT) X-Originating-IP: [178.200.247.30] In-Reply-To: <5a9e29cec281298b330aed14b41dddb9@nebm.ist.utl.pt> References: <4FC80163.3030500@gmail.com> <5a9e29cec281298b330aed14b41dddb9@nebm.ist.utl.pt> Date: Fri, 1 Jun 2012 10:02:53 +0200 Message-ID: To: Gustavo Lopes Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=f46d0401faed873d9e04c1649c08 X-Gm-Message-State: ALoCoQkTvGk4Ts6ObEOrHDbMnLZSM0AHjRWpR2zSu3q+0m7FRObsBqTS5yKSfrMT1ypxvtwOfD3m Subject: Re: [PHP-DEV] BreakIterator From: kontakt@beberlei.de (Benjamin Eberlei) --f46d0401faed873d9e04c1649c08 Content-Type: text/plain; charset=ISO-8859-1 How about IntlBreakIterator? I agree with David that the naming is very weird, it doesn't hint at something from Intl but another crazy spl iterator :-) On Fri, Jun 1, 2012 at 9:57 AM, Gustavo Lopes wrote: > On Fri, 01 Jun 2012 09:40:19 +1000, David Muir wrote: > >> Coming from a "pleb", my only concern is the name if the class is in the >> global scope. A "BreakIterator" to me sounds like something related to >> breaking out of a looping structure, and not something used for >> iterating over various language structure boundaries. >> If it's in a ICU namespace, then it's not a problem, as it's clearly >> related to Unicode. >> >> > We currently don't use namespaces in any of the core extensions. All the > other symbols in ext/intl are in the global namespace; to put BreakIterator > in a new namespace would be inconsistent -- and to put the whole extension > would be a huge BC break. > > As to the name chosen to the class, it just mirrors the name used in ICU. > In some cases, we prefixed the class name with Intl, in order to minimize > the likelihood of symbols collisions or distinguish it from other similar > functionality in PHP (something namespaces would be more appropriate for), > but otherwise we prefer to keep the symbols names used in ICU in order to > make it easy for people who already know the native API. > > Additionally, I think your concerns are exaggerated. The symbol > BreakIterator can only used in contexts where it's obvious it's a class > name, as in BreakIterator::**createWordInstance('en'). > > -- > Gustavo Lopes > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --f46d0401faed873d9e04c1649c08--