Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97515
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Wed, 4 Jan 2017 14:12:07 -0600
Message-ID: <2017010414120739532-pmjones88@gmail.com>
References: <0D388F9E-98FA-4C1F-95FA-759C4D4731C6@gmail.com> <2A.04.04761.F9A9D585@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
User-Agent: Unison/2.2
Subject: Re: [RFC] ServerRequest and ServerResponse objects
From: pmjones88@gmail.com (Paul M . Jones)

On 2016-12-23 21:43:56 +0000, Andrea Faulds said:

> Hi,
> 
> Since the $get, $post etc. properties are the same as $_GET and $_POST, 
> does that mean they retain the same name mangling scheme? (See "https 
> colon slash slash wiki dot php dot net slash rfc slash 
> on_demand_name_mangling"* for details of that.)
> 
> It would be nice to fix that eventually, and this would be a place 
> where we could do so without breaking backwards-compatibility.
> 
> *Sorry about spelling it out like that. Apparently, the mail server 
> thinks this link is spam.

(I'm trying to post via Usenet, since mailing list messages on this 
thread have not come through to me. This is a copy of an email I sent 
to Andrea directly.)

I presume the answer is "yes" because the properties are populated 
directly from $_GET and $_POST.

If there is some patch that might be applied to un-mangle things, and 
you think this is the place to do it, I cannot imagine John Boehr or I 
would refuse a patch.


-- pmj