Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33200
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sambarrow.com from 205.234.132.11 cause and error)
To: Sean Coates <sean@caedmon.net>
Cc: Michael McGlothlin <michaelm@swplumb.com>, internals@lists.php.net
In-Reply-To: <6743D10C-4AE9-4974-B0C3-3A632A0326F1@caedmon.net>
References: <8D.46.01128.768AD374@pb1.pair.com>
	 <1195246391.21084.15.camel@sbarrow-desktop>
	 <1195250285.4012.6.camel@johannes.nop>
	 <1195251014.21084.20.camel@sbarrow-desktop>  <473E349E.3050704@swplumb.com>
	 <1195259494.10547.2.camel@sams-room>
	 <0E6C7DB2-4126-4660-A813-E21C03045247@caedmon.net>
	 <473E5F4F.2020508@swplumb.com>
	 <6743D10C-4AE9-4974-B0C3-3A632A0326F1@caedmon.net>
Content-Type: text/plain
Date: Fri, 16 Nov 2007 23:18:36 -0500
Message-ID: <1195273116.12249.28.camel@sams-room>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Question about superglobals
From: sam@sambarrow.com (Sam Barrow)

You say that superglobals were not designed to be user defined, think
about it, the concept of a superglobal is present in C and C++, two of
the maturest and strictest languages around.

On Fri, 2007-11-16 at 22:34 -0500, Sean Coates wrote:
> > So the idea now is to inappropriately force everything to be a class?
> >>
> 
> It is appropriate. That's how it was designed. Obviously superglobals  
> were not designed to be user-definable.
> 
> If configuration is defined in a class, then as a maintainer, you can  
> easily determine where the data was defined (unless you do things are  
> even less appropriate), but simply looking up the class.
> 
> Globals (and superglobals) can be defined _anywhere_. This makes them  
> a maintenance nightmare, and a very inappropriate place to store data  
> such as configuration information.
> 
> S
>