Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85040 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96359 invoked from network); 16 Mar 2015 12:19:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 12:19:59 -0000 Authentication-Results: pb1.pair.com header.from=osrdek@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=osrdek@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender) X-PHP-List-Original-Sender: osrdek@gmail.com X-Host-Fingerprint: 74.125.82.52 mail-wg0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:35630] helo=mail-wg0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/85-03331-D6AC6055 for ; Mon, 16 Mar 2015 07:19:58 -0500 Received: by wgdm6 with SMTP id m6so38377144wgd.2 for ; Mon, 16 Mar 2015 05:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=G9WNm22iNY0uxxEGavLURPwoTBGVB/kwp/BL0LTE+xg=; b=mPc20STFBnq/E4n7SSg3wv3/2zD+eoTIAv9bnIBsnQSlQ/aQODeZGty2wKocBrqRUe znBDthtMkyzS3Ja+G+cRK1rluydOxpPnFf4TeeEyAzXINiS/hwk93YkdAZe7nlnEa2ie u/BLxhfHUqnLqjswX6RlTIi56XoLYPFY3abkepIs7O4LtMmfGgZLrSccA+Dww2N/EzKo Lo4sUDofegP8u9U2iKfPzVJXGETCkV5vgYUbL34aC9wWObOAbY5XV3yyn8+hitqNhAKz M8519s4Za4Vr9WmtWfbZbxpykZkkqw/O0vp4kamUgxcQ/K4Vzbv1JG253mL0pUEg6N7C GjAw== MIME-Version: 1.0 X-Received: by 10.194.61.244 with SMTP id t20mr117269528wjr.83.1426508394549; Mon, 16 Mar 2015 05:19:54 -0700 (PDT) Received: by 10.180.207.83 with HTTP; Mon, 16 Mar 2015 05:19:54 -0700 (PDT) In-Reply-To: References: <55066F07.80308@birkholz.biz> <5506794B.8090008@birkholz.biz> Date: Mon, 16 Mar 2015 13:19:54 +0100 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary=047d7b86e4062079ea051166de0b Subject: Re: [PHP-DEV] About declare(strict_types = 1) From: osrdek@gmail.com (Anton Osrdek) --047d7b86e4062079ea051166de0b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Mar 16, 2015 at 12:49 PM, Pavel Kou=C5=99il wr= ote: > Hello, > > it's similiar to the safe_mode though. Sure, it's not as bad as INI > setting, but the "intent" is the same - a switch changing how code > behaves. > > When I talked about the Dual Mode with some friends who are userland > PHP devs (either current or former, because they switched to other > stuff), none of them called the Dual Mode a great idea. The responses > I got were mostly along the lines of "wow, this seems really weird" to > "WTF are those developers smoking". Everyone of them (sure, ~10 people > isn't really representative number) said that they think PHP needs > STH, but not this Dual Mode stuff. > > Seriously, think about it for a while - when some setting that changes > how code behaves was a good idea? > > (IMHO never.) > > Regards > Pavel Kouril > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > I was like that in the beginning when Andrea introduced the declare syntax. But this was because of a fundamental misunderstanding how declare actually works. Now I think it's a brilliant solution to introduce optional strict type hinting. It does not force a user who uses week type hinting to use, care or even know about strict type hinting. --047d7b86e4062079ea051166de0b--