Idea for PHP Enhancement: register_global s_manual

[127.0.0.1]

With all the problems with having register_global s = on, I propose the
following idea:

We define register_global s_manual = on as a new configuration default.

What this does is enable 3 new explicit variable declaration mechanisms
with the same syntax as the existing static and global mechanisms.

They would be httpget, httppost and session, so for example:

httpget $user_id;
httppost $credit_card;
session $really_importa nt_stuff;

Each of these declaration lines would effectively enable
register_global s for one specific variable in one particular method
(GET, POST or session).

Creative suggestions, comments would be welcome.

--
Spam:newsgroup( at)cr*********@ verisign-sux-klj.com
EMail:<01100011 001011100110001 001110101011100 10011010110
110010101000000 011000110111001 001100001011110 10011011100
110000101110010 001011100110001 101101111011011 0100100000>

[Jon Kraft]

127.0.0.1 <newsgroup(at)c r*********@veri sign-sux-ijlkl.com> wrote:

Phil Roberts wrote:

But what is the POINT of your method when PHP has plenty of non-
register_global s reliant methods already?

It doesn't have one for SESSION variables yet ....

extract($_SESSI ON);

JOn

[127.0.0.1]

Jon Kraft wrote:

But what is the POINT of your method when PHP has plenty of non-
register_global s reliant methods already?

It doesn't have one for SESSION variables yet ....

extract($_SESSI ON);

How does that get a session variable 'X' into and out of $X ?

--
Spam:newsgroup( at)cr*********@ verisign-sux-klj.com
EMail:<01100011 001011100110001 001110101011100 10011010110
110010101000000 011000110111001 001100001011110 10011011100
110000101110010 001011100110001 101101111011011 0100100000>

[Jon Kraft]

127.0.0.1 <newsgroup(at)c r*********@veri sign-sux-ijlkl.com> wrote:

Jon Kraft wrote:

>> But what is the POINT of your method when PHP has plenty of non-
>> register_global s reliant methods already?
>
> It doesn't have one for SESSION variables yet ....

extract($_SESSI ON);

How does that get a session variable 'X' into and out of $X ?

extract() attempts to create variables (names = keys) from an associative
array.
The advantage of extract() is that it provides a high level of control
through the parameter "extract_ty pe", which a simple register_global
variant wouldn't.

JOn

[127.0.0.1]

Jon Kraft wrote:

extract($_SESSI ON);

How does that get a session variable 'X' into and out of $X ?

extract() attempts to create variables (names = keys) from an
associative array.

SO - how does that get session variable 'x' into and out of $x ?

--
Spam:newsgroup( at)cr*********@ verisign-sux-klj.com
EMail:<01100011 001011100110001 001110101011100 10011010110
110010101000000 011000110111001 001100001011110 10011011100
110000101110010 001011100110001 101101111011011 0100100000>

[Jon Kraft]

127.0.0.1 <newsgroup(at)c r*********@veri sign-sux-ijlkl.com> wrote:

Jon Kraft wrote:

>>
>> extract($_SESSI ON);
>
> How does that get a session variable 'X' into and out of $X ?

extract() attempts to create variables (names = keys) from an
associative array.

SO - how does that get session variable 'x' into and out of $x ?

Sorry, I don't get your question - if it is a question and not a rhetorical
statement that renders my suggestion useless?

Let's say we have a session variable "x" ($_SESSION['x']).
extract()'s default behaviour would result either in a new variable $x or an
assignment of the value of the session variable "x" to the existing
variable $x. If you assign another value to $x, it is overwritten (again),
which doesn't change the value of the session variable "x" unless you tell
extract() to create the (new) variables by reference (EXTR_REFS,
PHP>=4.3.0).

Please enlighten me if I totally misunderstood what you were after.

JOn

[127.0.0.1]

Jon Kraft wrote:

Please enlighten me if I totally misunderstood what you were after.

I'm after the ability to use the variable $x in a script, such that
between requests from the client it retains its value.

That is all.

By variable $x I mean $x, $fred, $user_id, not $_XZJ[14] or anything
else.

--
Spam:newsgroup( at)cr*********@ verisign-sux-klj.com
EMail:<01100011 001011100110001 001110101011100 10011010110
110010101000000 011000110111001 001100001011110 10011011100
110000101110010 001011100110001 101101111011011 0100100000>

[Kevin Thorpe]

127.0.0.1 wrote:

With all the problems with having register_global s = on, I propose the
following idea:

We define register_global s_manual = on as a new configuration default.

What this does is enable 3 new explicit variable declaration mechanisms
with the same syntax as the existing static and global mechanisms.

They would be httpget, httppost and session, so for example:

httpget $user_id;
httppost $credit_card;
session $really_importa nt_stuff;

Each of these declaration lines would effectively enable
register_global s for one specific variable in one particular method
(GET, POST or session).

Creative suggestions, comments would be welcome.

$user_id =& $_GET['user_id'];
$credit_card =& $_POST['credit_card'];
$really_importa nt_stuff =& $_SESSION['really_importa nt_stuff'];

works fine, I use it all the time.

[127.0.0.1]

Kevin Thorpe wrote:

$really_importa nt_stuff =& $_SESSION['really_importa nt_stuff'];

works fine, I use it all the time.

So the following would work ?

First Client Request...
session_start() ;
$X =& $_SESSION['X'];
$Y = 'Fred';
$X = $Y;

Second client request...
session_start() ;
$X =& $_SESSION['X'];
$Y = $X;
echo($Y); ... printing 'Fred'....

--
Spam:newsgroup( at)cr*********@ verisign-sux-klj.com
EMail:<01100011 001011100110001 001110101011100 10011010110
110010101000000 011000110111001 001100001011110 10011011100
110000101110010 001011100110001 101101111011011 0100100000>

[Jon Kraft]

127.0.0.1 <newsgroup(at)c r*********@veri sign-sux-ijlkl.com> wrote:

Jon Kraft wrote:

Please enlighten me if I totally misunderstood what you were after.

I'm after the ability to use the variable $x in a script, such that
between requests from the client it retains its value.

That is all.

By variable $x I mean $x, $fred, $user_id, not $_XZJ[14] or anything
else.

Check my previous reply (and the manual for extract()) for the extract_type
"EXTR_REFS" .
An assignment of a new value to $x would then in fact change the session
variable "x".

HTH;
JOn

[Justin Koivisto]

127.0.0.1 wrote:

Kevin Thorpe wrote:

$really_impor tant_stuff =& $_SESSION['really_importa nt_stuff'];

works fine, I use it all the time.

So the following would work ?

First Client Request...
session_start() ;
$X =& $_SESSION['X'];
$Y = 'Fred';
$X = $Y;

Second client request...
session_start() ;
$X =& $_SESSION['X'];
$Y = $X;
echo($Y); ... printing 'Fred'....

Yes, it would (see test script):

<?php
if(!isset($_GET['next'])){
// First Client Request...
session_start() ;
$X =& $_SESSION['X'];
$Y = 'Fred';
$X = $Y;
echo '$_SESSION[\'X\']: ',$_SESSION['X'],'<br>';
echo '$X: ',$X,'<br>';
echo '$Y: ',$Y,'<br>';
echo '<a href="?next">ne xt</a>';
}else{
// Second client request...
session_start() ;
$X =& $_SESSION['X'];
$Y = $X;
echo '$_SESSION[\'X\']: ',$_SESSION['X'],'<br>';
echo '$X: ',$X,'<br>';
echo '$Y: ',$Y,'<br>';
}
?>
--
Justin Koivisto - sp**@koivi.com
PHP POSTERS: Please use comp.lang.php for PHP related questions,
alt.php* groups are not recommended.