Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80613 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24841 invoked from network); 16 Jan 2015 02:18:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jan 2015 02:18:27 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.45 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.218.45 mail-oi0-f45.google.com Received: from [209.85.218.45] ([209.85.218.45:43441] helo=mail-oi0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 17/11-19143-FE478B45 for ; Thu, 15 Jan 2015 21:18:25 -0500 Received: by mail-oi0-f45.google.com with SMTP id x69so15425833oia.4 for ; Thu, 15 Jan 2015 18:18:21 -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=WbQjtFWcHN/Mz0FDWkXp0B3ROT0QL/RuBZpjR+5U7WM=; b=pdqGr7dyPPHS6zHGWtvFCXWYDlHhtIGD6QEDuINBveM4Ea5mGuNMyXE8NyTH02DuQz 3f+pli/jTewspZcg4hkDW2BPkaopYfIawpYO157HoLykRubaCFN7Rz0wz7FbwacoCpWL GWauxW9K7e4Mkf6zbG8JjQRDNqylLcJWwrRo6qFMReLyFJR0UGCHhrH3sdbvF0oEnc75 4AeOwbQhoHBugNt4J3Z4DaSI9x/RORgaEGK742PGogV3kcEjaccSnyTDcijVa2+M/bPG lalOsSMKsDnSQfkPTIvox5raTbkA/CZ7amCOE+jBYO80eFuU2ToMLvhXI9wgaFDyJ+Fj DGKQ== X-Received: by 10.182.40.200 with SMTP id z8mr8119122obk.38.1421374700970; Thu, 15 Jan 2015 18:18:20 -0800 (PST) Received: from [192.168.2.145] (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id c16sm1589615oih.6.2015.01.15.18.18.19 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jan 2015 18:18:20 -0800 (PST) Message-ID: <54B874E7.4010509@gmail.com> Date: Thu, 15 Jan 2015 18:18:15 -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: marcio3w@gmail.com CC: Andi Gutmans , Andrea Faulds , Zeev Suraski , Richard Quadling , 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> <6105ea99002e634373c09685310e26a6@mail.gmail.com> <85F6139E-6332-4645-91B8-C852B07EA62A@ajf.me> <12433808-9D62-48D3-B66E-74572C61BF68@zend.com> <54B85C2B.9000901@gmail.com> <54B86134.1020801@gmail.com> <54B86C63.6070802@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2 From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Even Nikic presented different versions of "strict" proposals on an > old article > http://nikic.github.io/2012/03/06/Scalar-type-hinting-is-harder-than-you-think.html I don't see "different versions" - I see one version of "strict" which matches my description and which he unequivocally opposes. What he supports is "weak type hints, but with stricter input validation". Which is not what the proposed RFC is calling "strict" - "With this approach, an argument is only accepted if its type is exactly the same as the parameter." - which again exactly the same as I said. So in this regard, myself, Andrea and Nikita are in full agreement about what "strict" means, however much we disagree in other aspects. -- Stas Malyshev smalyshev@gmail.com