Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82278 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44740 invoked from network); 9 Feb 2015 13:42:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Feb 2015 13:42:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.172 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.172 mail-qc0-f172.google.com Received: from [209.85.216.172] ([209.85.216.172:51275] helo=mail-qc0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/62-50460-859B8D45 for ; Mon, 09 Feb 2015 08:42:48 -0500 Received: by mail-qc0-f172.google.com with SMTP id x3so22416075qcv.3 for ; Mon, 09 Feb 2015 05:42:46 -0800 (PST) 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 :cc:content-type; bh=VmMtUxaMU1mqVeF/k4ui+htw/TdRzvw3l4dph7ZFl3Q=; b=IGggpeSTweYPFPZVRCgMeSpaqO0/AP8njIApWwvxWcrTOhLNOy7Y/OwiDXb72S17lS w1N3XfzonUClv9ugSYeALSyQ8yPtOkW/0SgFq63lQwZMR8rQz54zeTIy9ha2laUnl2us i6hyOs16kMIIzeuoDWEaR3sX1ANIPyLsQMsQpdgVYPOPd1tNbCuoEAOVNkRlvrLUzcm5 gjozixw2y+FKVc0TEECPBAIs+eJUvxpBQnAImtf3WydyN5zUVToeMagfkrGqGytNk3e3 akZi/S5jiZEfZ59gS//gYK527x1KhYKQb9ecg6tKwqsTB1AHQBJPRFClwvJWoNbImQPX JA5A== MIME-Version: 1.0 X-Received: by 10.224.171.67 with SMTP id g3mr34119129qaz.17.1423489357646; Mon, 09 Feb 2015 05:42:37 -0800 (PST) Received: by 10.96.185.37 with HTTP; Mon, 9 Feb 2015 05:42:36 -0800 (PST) Received: by 10.96.185.37 with HTTP; Mon, 9 Feb 2015 05:42:36 -0800 (PST) In-Reply-To: <04a501d04458$99d35880$cd7a0980$@tekwire.net> References: <04a501d04458$99d35880$cd7a0980$@tekwire.net> Date: Mon, 9 Feb 2015 20:42:36 +0700 Message-ID: To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= Cc: Yasuo Ohgaki , PHP internals , Matt Parker Content-Type: multipart/alternative; boundary=047d7b677688811111050ea7f109 Subject: RE: [PHP-DEV] scalar type hints From: pierre.php@gmail.com (Pierre Joye) --047d7b677688811111050ea7f109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Feb 9, 2015 6:07 PM, "Fran=C3=A7ois Laupretre" wr= ote: > > > De : Pierre Joye [mailto:pierre.php@gmail.com] > > > > > However, DbC is coming close! > > > > > > DbC brings much more flexibility, strict/loose constraints, performance, > > > security, better documentation and more. > > > DbC suitable for weakly typed PHP perfectly. > > > > > > Therefore, I'm holding my vote now. > > > I hope everyone have an attention to DbC and consider thoughtfully. > > > > Imho they are totally different things. > > You're right. That's two different things in the way they are implemented. But they are also closely related because both approaches propose an element of solution to similar needs: reduce coding errors. > > Then, depending on their own position about strict types, people will consider it as just a complement, or as a whole alternative. I agree on one thing, we mustn't mix both discussions :) It is not what I am saying. Let me try with a fictional example. Let say we have a RFC about adding support to comments in code. Yes, simple comments. Now what has been said here is that he suspends his vote because there is other working on adding phpdoc. And comparing DbC with type hinting is light years different. --047d7b677688811111050ea7f109--