Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82037 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24295 invoked from network); 6 Feb 2015 10:40:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Feb 2015 10:40:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.175 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.220.175 mail-vc0-f175.google.com Received: from [209.85.220.175] ([209.85.220.175:51672] helo=mail-vc0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2E/6F-45146-80A94D45 for ; Fri, 06 Feb 2015 05:40:09 -0500 Received: by mail-vc0-f175.google.com with SMTP id la4so4738695vcb.6 for ; Fri, 06 Feb 2015 02:40:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=/Y7KDpAuAdNrDMyt+1XH2CEHi8TneWxTvtlVQZYF9yI=; b=iGX7vflOpYdFa059FsqR6RO9auJ3dHQt/79Za6T3OJngwHoMjkwJjTKO0XX9msco7L ctOPcYss/Q8a8HaBjXF/tETZZ2sTinGJPyeKPZcL5OY1KMBNNNJ3IC2q8QvOAIJfrOfC G64ggOp8NQFIJr6iUd2HZuX9ZK43x/72mvxY5k9UToX80BoC+96UzsMGTd4pHIXhfrKc 6v0E009gm1oMEVzSYhEczBPOFHc0U7ZMWkW+LyH9VMQkYfMov92mx6dmiMqh6PGWc5JQ KFFRd8WniXG/YF9cn7SnIPTfX+Ovv3/0/CPYlQLajEr7M//lgs6UF8FI0AguPbG04NzQ qRRQ== X-Gm-Message-State: ALoCoQlAvuhWumx7nUmuKHyw3KGd9MSHOVWSKvpwgMfMirYOwuh4mwnJa3dShQQpQWkjxKj+z48flvHN3GCtHeY0kMjWh1L27sL9FkhjjTXGtA+gkya7dJycXAYmak4ssA+U+XdYD0NG6RDSy5s4YL8z+ZLF5nrnXQ== MIME-Version: 1.0 X-Received: by 10.220.185.193 with SMTP id cp1mr1725201vcb.80.1423219205718; Fri, 06 Feb 2015 02:40:05 -0800 (PST) Received: by 10.52.74.73 with HTTP; Fri, 6 Feb 2015 02:40:05 -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 14:40:05 +0400 Message-ID: To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= Cc: Yasuo Ohgaki , "Ivan Enderlin @ Hoa" , PHP Internals Content-Type: multipart/alternative; boundary=089e0153861031de66050e690b29 Subject: Re: [PHP-DEV] Design by Contract From: dmitry@zend.com (Dmitry Stogov) --089e0153861031de66050e690b29 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable this is not going to be a BC break, this is going to be a Forward Compatibility break, that won't allow PHP code that use this feature work on PHP5. Scalar type hints and attributes are also going to introduce such breaks. On the other hand if we keep constraints in phpdoc, PHP core shouldn't care about it at all, and DbC is going to be a goal for separate project (like phpDocumentor). Alexander, already have AOP based implementation. In this moment, I don't have strong opinion, if we really need support for DbC in PHP language (like in D). Thanks. Dmitry. Thanks. Dmitry. On Fri, Feb 6, 2015 at 12:55 PM, Fran=C3=A7ois Laupretre wrote: > Hi Yasuo, > > > 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. > > Cheers > > Fran=C3=A7ois > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --089e0153861031de66050e690b29--