Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59827 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41997 invoked from network); 13 Apr 2012 00:56:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2012 00:56:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.203 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.203 smtp203.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.203] ([67.192.241.203:38109] helo=smtp203.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 45/9D-00290-2A9778F4 for ; Thu, 12 Apr 2012 20:56:02 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp10.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 21D981B817F; Thu, 12 Apr 2012 20:55:59 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp10.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id B4A6D1B81B0; Thu, 12 Apr 2012 20:55:58 -0400 (EDT) Message-ID: <4F87799D.4060601@sugarcrm.com> Date: Thu, 12 Apr 2012 17:55:57 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Yasuo Ohgaki CC: PHP internals References: <4F8539E0.1090701@sugarcrm.com> <4F859063.1010401@lerdorf.com> <4F862AAC.90003@lerdorf.com> <4F86761A.9010801@lsces.co.uk> <4F876E36.1020400@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Disabling PHP tags by php.ini and CLI options From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > If I exclude current code, then introducing script only include will be > preferred one. I preferred dedicated statement for it though. > > include > include_once > require > require_once > script > script_once I have a thought here. To implement script/script_once you don't need it to be a language construct. A function would do just as fine. Why not make an extension having these two functions, put it on PECL and see if people will be using it? For extreme adopters, you could even make php.ini switch that overrides include/require and redirects them to your script functions. Shouldn't be impossible to do, I think. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227