Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85079 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86166 invoked from network); 16 Mar 2015 18:29:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 18:29:49 -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:50148] helo=mx01.nexxes.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/D7-34940-A1127055 for ; Mon, 16 Mar 2015 13:29:49 -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 89ADA482445 for ; Mon, 16 Mar 2015 19:29:43 +0100 (CET) Message-ID: <55072117.70409@birkholz.biz> Date: Mon, 16 Mar 2015 19:29:43 +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: <55033D61.8050405@lsces.co.uk>, In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] STH and the 3 RFCs From: dennis@birkholz.biz (Dennis Birkholz) Hi Thomas, Am 16.03.2015 um 15:33 schrieb Thomas Punt: > A library can easily expose a facade that enforces a user of that library > (who is in weak mode) to have to write in strict mode [1]. Once more, > this can be done unintentionally [2] because of the > caller-deciding semantics. These examples can be further extended into wrapper > classes, nested library dependencies, etc. if the library author wants to fuck up his or her users, that library will be forgotten very fast. And exposing a non hinted interface and then using the received variables in strict mode is either fucking up the user or just a bug. Greets Dennis