(a) I agree that the names are long
(b) Remember that you can change the name by simply assigning it around
(e.g., $GET_A = $HTTP_GET_VARS)
(c) I think that $GET_A is ugly :) I'd go for something along the lines of
$__GET
(d) Having these variables available on every function means that it's
At 14:07 7/2/2001, Derick Rethans wrote the following:
--
Hello list,
sometimes I use PHP too, and today I noticed the things I described here.
Per coincidence, Jani, who is working on the new bugsystem, had the same
thoughts about
On Mon, 2 Jul 2001, Zeev Suraski wrote:
(a) I agree that the names are long
(b) Remember that you can change the name by simply assigning it around
(e.g., $GET_A = $HTTP_GET_VARS)
I know this, but then you'll end up with:
$GET_A = $GLOBALS[HTTP_GET_VARS];
$POST_A = $GLOBALS[HTTP_POST_VARS];
/me smells $@, $#, $$, $' and stuff. :|
I don't really mind PHP being a bit verbose.
At 15:10 7/2/2001, Zeev Suraski wrote the following:
--
(a) I agree that the names are long
(b) Remember that you can change the name by simply
On Mon, 2 Jul 2001, Cynic wrote:
/me smells $@, $#, $$, $' and stuff. :|
I don't really mind PHP being a bit verbose.
There is nothing wrong with being verbose of course, but there is a limit
on this. Writing 50 lines of code, and using in there around 20 times
$HTTP_SESSION_VARS or something
