Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50923 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64596 invoked from network); 9 Dec 2010 10:22:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2010 10:22:29 -0000 Authentication-Results: pb1.pair.com smtp.mail=james.butler@edigitalresearch.com; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=james.butler@edigitalresearch.com; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain edigitalresearch.com does not designate 217.154.180.62 as permitted sender) X-PHP-List-Original-Sender: james.butler@edigitalresearch.com X-Host-Fingerprint: 217.154.180.62 analysis.edigitalresearch.com Linux 2.6 Received: from [217.154.180.62] ([217.154.180.62:48018] helo=mail.edigitalresearch.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/A0-61607-4EDA00D4 for ; Thu, 09 Dec 2010 05:22:28 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.edigitalresearch.com (Postfix) with ESMTP id 87FD11816CC; Thu, 9 Dec 2010 10:22:23 +0000 (GMT) X-Virus-Scanned: amavisd-new at edigitalresearch.com Received: from mail.edigitalresearch.com ([127.0.0.1]) by localhost (mail.edigitalresearch.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VrxXYurX5xAE; Thu, 9 Dec 2010 10:22:22 +0000 (GMT) Received: from zarafa.localdomain (unknown [10.0.0.20]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.edigitalresearch.com (Postfix) with ESMTPS id CF5131816C8; Thu, 9 Dec 2010 10:22:22 +0000 (GMT) Received: from zarafa.edigitalresearch.com (zarafa.edigitalresearch.com [10.0.0.20]) by zarafa.localdomain (Postfix) with SMTP id D09F2100B27; Thu, 9 Dec 2010 10:22:22 +0000 (GMT) To: =?windows-1252?Q?Andrey_Hristov?= , =?windows-1252?Q?PHP_Internals_List?= Date: Thu, 9 Dec 2010 10:22:22 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable In-Reply-To: <4D00ABFE.5070403@hristov.com> References: <4D00ABFE.5070403@hristov.com> X-Priority: 3 (Normal) X-Mailer: Zarafa 6.40.2-22452 Thread-Index: AcuXiveN20DypcYaT22FHpQ+yN0FtQ== Message-ID: Subject: RE: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only From: james.butler@edigitalresearch.com (=?windows-1252?Q?James_Butler?=) +1 million because GLOBAL scope is horrid (generally) and is thoroughly abused -1 million because it will be the most horrific BC break since time began and I imagine it will break so much code that is currently in the wild... In short I like it but I'm not sure how it would ever get implemented without breaking stuff... (this is where the clever core developers can propose some easy method I can't think of right now) -----Original Message----- From: Andrey Hristov [mailto:php@hristov.com]=20 Sent: 09 December 2010 10:14 To: PHP Internals List Subject: [PHP-DEV] Deprecating "global" + $GLOBALS, making $_REQUEST, $_GET, $_POST read-only Hi guys, the topic says most of it. What do you think about deprecating the=20 global keyword and $GLOBALS with it=3F Together with this making=20 $_REQUEST, $_GET and $_POST read-only as they should be used only to=20 read-only anyway. The reason for global + GLOBALS is that these are abused and which leads=20 to spaghetti programs, when used by unexperienced users. Also they have=20 impact on side effects from functions that don't only rely their parameters. Best, Andrey --=20 PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php