Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82478 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29258 invoked from network); 11 Feb 2015 14:14:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2015 14:14:39 -0000 Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:37024] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B0/17-22055-EC36BD45 for ; Wed, 11 Feb 2015 09:14:39 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id C932E4B0239; Wed, 11 Feb 2015 15:11:00 +0100 (CET) Reply-To: To: "'Lester Caine'" , References: <54DAFD32.3000005@gmail.com> <54DB0BC0.20304@gmail.com> <54DB284B.4050306@lsces.co.uk> In-Reply-To: <54DB284B.4050306@lsces.co.uk> Date: Wed, 11 Feb 2015 15:14:32 +0100 Message-ID: <068a01d04605$0f06d070$2d147150$@tekwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGgxP9HPTh52uHWkGo6jLSeXRdtNAL8o2LiAeObGYcBWQpzyAF80lt6AYdLNZkBUtBHNAKheVawAYHgeoUCwMmB6QI4B688Af2JTIQBeFCubgJqfABAAeyFdV8BGv6aCpxl26lA Content-Language: fr X-Antivirus: avast! (VPS 150210-1, 10/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Design by Contract From: francois@tekwire.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) Hi Lester, > All of the current demands ... and I think they are demands! ... stamp > on past history and load even more work on everybody to have to = support > all these new features. Even if dbc is wrapped in comment blocks to = hide > it it's potential presence in third party parts of a project means = that > all tools have to be modified and my use of phpdoc is further eroded. The proposal to embed DbC conditions in phpdoc is just defining new '@' = keywords. That's the implicit way such a basic annotation system works : = tools ignore the lines they don't understand. I ran phpDocumentor on = DbC-commented script files, and it still produces the same = documentation. It's supposed to be the same with everyone extending = phpdoc syntax. So, I don't understand why you should modify any of your tools. Cheers Fran=C3=A7ois