Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26323
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cschneid.com from 195.226.6.42 cause and error)
Message-ID: <454CBD65.5040205@cschneid.com>
Date: Sat, 04 Nov 2006 17:18:45 +0100
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: Ilia Alshanetsky <ilia@prohost.org>
CC:  internals@lists.php.net
References: <005e01c6ff82$e6092c30$ec01010a@intranet.db> <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org>
In-Reply-To: <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New Datetime class problem
From: cschneid@cschneid.com (Christian Schneider)

Ilia Alshanetsky wrote:
> Avoid common namespaces and you'll make your application futureproof. 

I'm still wary of this approach because it puts the burden on 99% of the 
code to be written (applications) instead of a small, controllable 
subset (core and libraries).

> When developing a distributed application it is always a good idea to 
> prefix functions/class names with app name or some acronym to avoid 
> overly long names. The way things are going you are going to see more 
> and more classes being introduced by "core" PHP as well as the growing 

... which brings us back to the discussion of namespaces and which one 
core classes should use ;-)

> number of PECL extensions out there and I am not even going to mention 
> the thousands of libraries out there.

Those are less of a problem because you don't have to include them if 
you don't want to.

- Chris