Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60715
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 01 Jun 2012 17:02:54 +0200
To: Maciek Sokolewicz <maciek.sokolewicz@gmail.com>, internals PHP
 <internals@lists.php.net>
Organization: =?UTF-8?Q?N=C3=BAcleo_de_Engenharia_Biom=C3=A9dica_do_Insti?=
 =?UTF-8?Q?tuto_Superior_T=C3=A9cnico?=
In-Reply-To: <4FC8C511.9070307@php.net>
References: <ef6e6488aa70f76ccfe540098b54de83@nebm.ist.utl.pt>
 <4FC80163.3030500@gmail.com>
 <5a9e29cec281298b330aed14b41dddb9@nebm.ist.utl.pt>
 <CAEPJduncwgHkXXmjeMwE5Dpt9-ma1iby+WDVjLMvauzwRZJm4A@mail.gmail.com>
 <CAEZPtU6i6V1LfTAJVWBQwOe8izVtLzpyEcPmSPAtSgpsajo4fA@mail.gmail.com>
 <272fe309cbfd77b8c2331c9268282d95@nebm.ist.utl.pt>
 <4FC8C511.9070307@php.net>
Message-ID: <046ad7137069ac360e9c722c9588e415@nebm.ist.utl.pt>
User-Agent: RoundCube Webmail/0.5.3
Subject: Re: [PHP-DEV] BreakIterator
From: glopes@nebm.ist.utl.pt (Gustavo Lopes)

On Fri, 01 Jun 2012 15:35:13 +0200, Maciek Sokolewicz wrote:
> In my personal opinion, all Intl classes should be prefixed with
> Intl. It's not so much that BreakIterator is a very common name, but
> rather a very ambiguous name that may point to many different things.
> Just by the fact that multiple people have already posted here that 
> at
> first they thought BreakIterator had something to do with the break
> statement gives you a rather solid hint that the function of this
> class is not immediately clear. Prefixing it with Intl immediately
> makes it clear that it belongs to the Intl superfamily, and limits 
> the
> potential misunderstandings a lot. I actually still don't understand
> why not all Intl classes are prefixed? Isn't that the usual 
> procedure?
> eg. for MySQLi, and pretty much all other extensions?
>

We've had the convention of prefixing function names with some 
extension prefix, but this convention has not been as marked for class 
names -- perhaps because there were so not many of them and so there 
were less collision/confusion problems.

In any case, I'll rename the classes before merging.

-- 
Gustavo Lopes