Just passing this along form Ramsi... who sent it to me instead of the list.
(unless he wants to unsubscribe from my point of view :P )-----Original Message-----
From: Ramsi Sras [mailto:[EMAIL PROTECTED]]


Brian Tanner schrieb:

Brian Foddy actually brings up a really important issue, which would go
along way to making (at least me) much happier with the proposed change.

*If* there will be:


-- can we also have something else to the tune of:

$_External or $_User or $_Something

That gets populated based on the ordering set for GPC right now in the .ini
file?  I think it would go really far towards helping a newbie (and to
helping people fix their existing code), if there was one place that they
could look, to find the old value that they are now missing.

People can still go to _Get, _Post, and _Cookie if they require that level
of granularity, but I think most will be happy with a general container for
what Register_Globals *would* have done.

-Brian T

-----Original Message-----

If I can just interject once, I was a bit skeptical of this thread at
but I'm starting to come around to Zeev's point of view.  Security aside
(which I know it shouldn't be) I found in my own coding I always started
naming post or get variables like
$form_user_name or $post_user_name so I could easily tell just by
looking at individual sections of the code that this variable was web
input, vs my own internal variable.  But even still, it can be confusing
to newbes trying to understand "just how did this variable get its
Having the $_GET[
"post_user_name"] is much more straight forward.

But is there a $_POST call also?  Making a important distinction between
data posted or getted input?  If so, that may be a small inconvienence.

Good debate tho, and well timed for other issues I'm dealing with.


PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to