Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33217
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: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: internals@lists.php.net
In-Reply-To: <473E8E97.6060608@lerdorf.com>
References: <8D.46.01128.768AD374@pb1.pair.com>
	 <473E6F38.4020008@lerdorf.com> <1195274394.12249.34.camel@sams-room>
	 <200711162354.34489.larry@garfieldtech.com>
	 <1195279274.12249.40.camel@sams-room> <1195279545.12249.47.camel@sams-room>
		 <473E87C5.4090200@lerdorf.com> <1195280474.12249.60.camel@sams-room>
		 <1195281053.1702.8.camel@blobule> <1195281606.12249.69.camel@sams-room>
	  <473E8E97.6060608@lerdorf.com>
Content-Type: text/plain
Date: Sat, 17 Nov 2007 02:08:20 -0500
Message-ID: <1195283300.12249.73.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)

Ok forget it if anyone wants the patch just send me an email. By the way
i didn't mention it also includes a function that retrieves the list of
current superglobals.

On Fri, 2007-11-16 at 22:47 -0800, Rasmus Lerdorf wrote:
> Sam Barrow wrote:
> > I don't understand, people keep telling me this can cause problems so
> > it's trash. Really? Functions and variables can cause problems too. Not
> > to mention user input. Programming is not easy, but the more flexible it
> > is the better. I think it's up to the programmer to keep track of his
> > variables, rather than us limiting his functionality, just incase he
> > makes a mistake.
> > 
> > Any programmer can write bad code and it won't work. If he uses
> > superglobals he should understand that he needs to document them, it's
> > that simple. If that's too difficult, don't create a superglobal then,
> > great.
> > 
> > And if this isn't good enough, fine. Require an underscore for
> > superglobals to differentiate them even more. I'll write the code
> > myself, no problem.
> 
> We simply don't think this flexibility makes up for the potential
> confusion it can cause.  It isn't solving something that can't be done,
> it is just changing a minor syntax and concept which has been in place
> for the past 12 years of PHP.  To be completely blunt, this change has
> no chance of making it into PHP.  If you want it, you will have to
> maintain your own patch.
> 
> -Rasmus
>