Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84799 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16054 invoked from network); 15 Mar 2015 02:49:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2015 02:49:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=dennis@birkholz.biz; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=dennis@birkholz.biz; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain birkholz.biz does not designate 144.76.185.252 as permitted sender) X-PHP-List-Original-Sender: dennis@birkholz.biz X-Host-Fingerprint: 144.76.185.252 mx01.nexxes.net Received: from [144.76.185.252] ([144.76.185.252:33861] helo=mx01.nexxes.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 30/B2-01144-F43F4055 for ; Sat, 14 Mar 2015 21:49:52 -0500 Received: from [137.226.183.192] (ip3192.saw.rwth-aachen.de [137.226.183.192]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: db220660-p0g-1@packages.nexxes.net) by mx01.nexxes.net (Postfix) with ESMTPSA id 56D35482441 for ; Sun, 15 Mar 2015 03:49:48 +0100 (CET) Message-ID: <5504F34C.5090106@birkholz.biz> Date: Sun, 15 Mar 2015 03:49:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] A plea for unity on scalar types From: dennis@birkholz.biz (Dennis Birkholz) Hi together, Am 14.03.2015 um 14:37 schrieb Peter van Fessem: >> If a dev turns a file that he or she wrote into strict mode, then that >> only counts for that specific file. If you take over some code, then you >> can remove the declare line. *none* of those things you'd be able to do >> with ini settings. So don't shout out that nonsense FUD. > > It's equivalent to an ini setting in that it changes the behavior of the > code based on something that is declared elsewhere. Obviously a declare > statement in the top of the file is a lot better than an ini setting, > but I think the principle is the same. that is simply not true. The principle is not the same. The principle is roughly the same as with namespaces. If you are unsure, got to the top of the file, finished. Ini-Settings are runtime-dependent so there is no way to find out what the ini-setting will be beforehand. I think nobody will argue that namespaces are to complicated because you can define the current namespace at the top of a file which than changes the behavior of the file completely (which it does, somehow, by the way). Greets Dennis