Re: Proposal: CHANGELOG

From: Date: Wed, 11 Aug 2004 17:36:58 +0000
Subject: Re: Proposal: CHANGELOG
References: 1 2  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969363048@lists.php.net to get a copy of this message
Gabor Hojtsy wrote:
I thought about this but here's why I went with one description. First, the short definition (purpose) is already in the refpurpose of the function. Also, writing a summary for each would be a bit too difficult. As far as using just the first para, I think it'd be confusing having it so far apart from the rest of the description as they are often tied together. And something to keep in mind is long descriptions are rare. I agree return values should go after the parameter list. So here's my thoughts on the matter: Description (full) Parameter List Return Values Changelog Examples See Also The changelog has important information, enough so that it should go before the examples. I believe the only part that needs further discussion and thought is the Description.
Chagelog affects parameters, return values, and other types of behaviour, so it should be after the description of these IMHO. I am fine with Philip's above suggestion.
Fine with me too. Mehdi

« previous php.doc (#969363048) next »