Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82480 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33682 invoked from network); 11 Feb 2015 14:35:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2015 14:35:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:40907] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7B/E7-22055-FB86BD45 for ; Wed, 11 Feb 2015 09:35:46 -0500 Received: (qmail 10766 invoked by uid 89); 11 Feb 2015 14:35:41 -0000 Received: by simscan 1.3.1 ppid: 10755, pid: 10761, t: 0.1302s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 11 Feb 2015 14:35:41 -0000 Message-ID: <54DB68BC.5050807@lsces.co.uk> Date: Wed, 11 Feb 2015 14:35:40 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54DAFD32.3000005@gmail.com> <54DB0BC0.20304@gmail.com> <54DB284B.4050306@lsces.co.uk> <068a01d04605$0f06d070$2d147150$@tekwire.net> In-Reply-To: <068a01d04605$0f06d070$2d147150$@tekwire.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Design by Contract From: lester@lsces.co.uk (Lester Caine) On 11/02/15 14:14, François Laupretre wrote: >> 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. While phpDocumentor can ignore elements it does not understand, that information would be useful to maintain, so some modification of it's parsing would be appropriate. But I was referring more to the other proposals for adding essentially the same information, and how that might be hidden in non-docblock comment packets. But currently some tools are lagging behind even current changes in PHP and phpDocumentor does not get everything right already. I can't get a clean set of documents currently with either the original version or the Mk2 version of phpDocumentor on code that has produced clean documents in the past. Just another area that needs time spending to work out what now need updating which does not affect the working code. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk