Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50922
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain thelounge.net designates 91.118.73.15 as permitted sender)
Message-ID: <4D00AD47.8030200@thelounge.net>
Date: Thu, 09 Dec 2010 11:19:51 +0100
Organization: the lounge interactive design
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc13 Lightning/1.0b3pre Thunderbird/3.1.6
MIME-Version: 1.0
To: Andrey Hristov <php@hristov.com>
CC: PHP Internals List <internals@lists.php.net>
References: <4D00ABFE.5070403@hristov.com>
In-Reply-To: <4D00ABFE.5070403@hristov.com>
OpenPGP: id=7F780279;
	url=http://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigE4BC46A10AC61862D197A67F"
Subject: Re: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST,
 $_GET, $_POST read-only
From: h.reindl@thelounge.net (Reindl Harald)

--------------enigE4BC46A10AC61862D197A67F
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Please do not

global + GLOBALS can be used in so many ways and you would break
200.000 LOC only here which is running with reporting E_STRICT
in a production environment

The same for making $_GET/$_POST/$_REQUEST readonly
I know that it is not best practice, but sometimes
it makes life easier to fetch $_POST in a method
which overwrites a parent method and add a single
item before the parent is processing $_POST

Yes, there are many other ways to do the same but
BC-breaking trigger a lot of work and testing

Am 09.12.2010 11:14, schrieb Andrey Hristov:
>  Hi guys,
> the topic says most of it. What do you think about deprecating the glob=
al keyword and $GLOBALS with it? Together
> with this making $_REQUEST, $_GET and $_POST read-only as they should b=
e used only to read-only anyway.
>=20
> The reason for global + GLOBALS is that these are abused and which lead=
s to spaghetti programs, when used by
> unexperienced users. Also they have impact on side effects from functio=
ns that don't only rely their parameters.
>=20
> Best,
> Andrey


--=20

Mit besten Gr=C3=BC=C3=9Fen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofm=C3=BChlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/


--------------enigE4BC46A10AC61862D197A67F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0ArUgACgkQhmBjz394AnlEHQCfb0JuXv3DZ5Qejjyj9UNN46jR
nWgAn04xUxbFT4JQSfQ+igcAf9IJGaiI
=pJej
-----END PGP SIGNATURE-----

--------------enigE4BC46A10AC61862D197A67F--