Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80503 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79015 invoked from network); 14 Jan 2015 23:29:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jan 2015 23:29:35 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.44 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.218.44 mail-oi0-f44.google.com Received: from [209.85.218.44] ([209.85.218.44:46564] helo=mail-oi0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/72-00659-FDBF6B45 for ; Wed, 14 Jan 2015 18:29:35 -0500 Received: by mail-oi0-f44.google.com with SMTP id a141so9897871oig.3 for ; Wed, 14 Jan 2015 15:29:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=UffnZRQUb+Rse61SQlvbSaAdOsQ225haatNnCHonU60=; b=vv2DLjCwgSEvahGm1ZrbStAifVHSg4TslCEqLuNNetZoQh6dYW2gn0hwDtGhuNiYQw 8Ol0wpYwyhuyv0sn3H4Pv8Pjqq07Abi7UqbvW0kVrbk+23VT8BHqRe5ooEpgdg6GQoBZ gqYWFmski5m1x6bqC71ICXEB2DCjexCUpEUs2X5Mw21QYgPkyodIkco6G2Okbw8R70PQ +/rVl0/vMEMSjK5y2vl2ZFqgynkrGy7arGt8zMhyiaBiwtecYIOkDsIm3kA4M+kbhl3k vyq5xqqQCFf43hmJ5X5Mb5NoI3F3U/kenDUl24LmgFsZZflsv4dm7sEu5N9KrDxmyfU9 lTNA== X-Received: by 10.202.59.136 with SMTP id i130mr3818802oia.114.1421278172868; Wed, 14 Jan 2015 15:29:32 -0800 (PST) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id o5sm12752021obz.9.2015.01.14.15.29.31 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jan 2015 15:29:31 -0800 (PST) Message-ID: <54B6FBD8.9050109@gmail.com> Date: Wed, 14 Jan 2015 15:29:28 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Zeev Suraski , RQuadling@gmail.com CC: Andrea Faulds , Leigh , PHP Internals List References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me> <9a033dd1f223f854e760924d118ab812@mail.gmail.com> <2ae0164cb9b9bf1c974d7a3c60af0466@mail.gmail.com> In-Reply-To: <2ae0164cb9b9bf1c974d7a3c60af0466@mail.gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2 From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > We’re definitely not going to have consensus on introducing both options as > per this RFC. I for one think it’s the worst possible option. I agree. Being wrong is bad, making a mistake is bad, but having split personality language and not knowing in which world you are - or even worse, having to deal with both worlds in the same code and being thrown back and forth between them by some little switch which is easy to miss - IMO is worse. I don't like strict typing in PHP because I think it is contrary to the idea of how dynamic languages should work, but I'd rather have that then two sets of rules living within the same code, especially when looking at the function I can't even know how it would work without checking if there's a declare hiding somewhere. And refactoring becomes a nightmare - what if I moved function from strict world to non-strict world or vice versa? I also agree with Dmitry in other thread - if some conv rules are so bad everybody hates them (or at least you think it is the case :), we can change them. We are already on that track with some weird ones like array->string. Even with BC effects, IMO better than too many sets of rules. -- Stas Malyshev smalyshev@gmail.com