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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
