Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82036 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22524 invoked from network); 6 Feb 2015 10:34:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Feb 2015 10:34:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.47 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.47 mail-qg0-f47.google.com Received: from [209.85.192.47] ([209.85.192.47:52205] helo=mail-qg0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 02/1F-45146-7C894D45 for ; Fri, 06 Feb 2015 05:34:47 -0500 Received: by mail-qg0-f47.google.com with SMTP id l89so10482820qgf.6 for ; Fri, 06 Feb 2015 02:34:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=jP+l0nTgiv5GhWr3bQ5qEwhTxX1eFFCZKaNDBHeGW6U=; b=zvL6Phtx5t3n1v9NxwSWyNufKll4UHJhYvvr1HJedhJ8X7vmAG4aT3VpioufFRC9C8 ihxqPE07iJul/HwmJyB7JUt6n5SfLVBXiA1R83itPsRbi/37XNaxQJggDYy2ejN7dOiX 6zq7VBLvvZUo1AL4b/N7JT+hfwj/V1d5PcHSs8wgtSpD9+S2nwwJipVMnRz9u3JheewZ OqKJARFYtNqv0MQJqAZryT3EFTTrDkP9mZm41hAMRZlYsbzm1SaTNGeG0MjjvRj6E1l/ 089ccXSdcfs+G23bVDFypNxelAPwirs9O9IFWX1tWrh05lotEPKN9p/pHWL7TQd5t00e oXzA== X-Received: by 10.140.90.112 with SMTP id w103mr6187493qgd.65.1423218885033; Fri, 06 Feb 2015 02:34:45 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.28.72 with HTTP; Fri, 6 Feb 2015 02:34:04 -0800 (PST) In-Reply-To: <02d301d041f3$0c5f3990$251dacb0$@tekwire.net> References: <54D37D41.2030706@hoa-project.net> <54D470FA.6000303@hoa-project.net> <02d301d041f3$0c5f3990$251dacb0$@tekwire.net> Date: Fri, 6 Feb 2015 19:34:04 +0900 X-Google-Sender-Auth: RF-OwFdcGuOlb4WBTDFDUVwq3cE Message-ID: To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= Cc: "Ivan Enderlin @ Hoa" , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c11a981486c6050e68f81d Subject: Re: [PHP-DEV] Design by Contract From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c11a981486c6050e68f81d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Francois, On Fri, Feb 6, 2015 at 6:55 PM, Fran=C3=A7ois Laupretre wrote: > > De : yohgaki@gmail.com [mailto:yohgaki@gmail.com] De la part de Yasuo > Ohgaki > > Do you think of any negative impact on PHP if we implement D like > > in{}/out{} which allow any PHP syntax? > > Can you please give your opinion about the BC break a D-like syntax would > introduce ? It is important because, if the community accepts such a BC > break for PHP 7, I stop working on my proposal based on phpdoc comments. > IMO, it is essential to offer DbC option without making the 'DbC-enabled' > code unable to run on PHP 5, but that's just my opinion. I can understand motivation to write script runs in older release. It's nice, I agree. Personally, backward compatibility is not too important. PHP5 is dead by PHP 7.2 release... This is the reason why. It's only 3 years later, only 2 years later after PHP 7.0 release. Therefore, I prefer PHP syntax based one. If it could be written as normal PHP code, it would be great. I prefer my proposal of course. However, I don't care much about where it should be written. I only care we have clean/fast/native/easy DbC support in PHP 7. I thought you are going to write PHP syntax borrowed one. For most users, PHP syntax is better. IMHO. Since Dmitry offered something based on annotation, could you work based on PHP syntax? and show us your concept on this thread? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c11a981486c6050e68f81d--