I much rather see time spent on getting the docs complete for the current version, though. Compared to that I think version info in the manual is of little value.
Perhaps this is brought up because there are no good manuals for older versions? I.e. people rather look in the latest manual because most things actually are documented there and then sees this problem when they find that the stuff mentioned in the docs doesn't exist in their version? Then the problem is the lack of good old manuals, and, well, the interest for writing complete manuals for 0.6, 7.0 and 7.2 is probably not overwhelming.. :\
/ Martin Stjernholm, Roxen IS
Previous text:
2003-02-07 01:47: Subject: Re: API version tagging
On Fri, Feb 07, 2003 at 01:30:01AM +0100, Martin Nilsson (Åskblod) @ Pike (-) developers forum scribbled:
Well, I guess it's ok for developers like us, but people coming in to learn pike wouldn't rather be happy if they had to jump between two (or more) sets of documentation.
Why would someone new to Pike be interested in API changes in the first place?
Because they would have started using Pike 7.4 and are interested in Pike 7.5, for example. Or any casual coder who wants to ensure that his/hers scripts will run on several machines with various pike versions. Or not-so-casual coders who want the same but are (understandably) to browse two huge docsets just to find the information that should be readily available at the first sight. Maybe I'm wrong, but such "details" also add up to the quality of software. And, as we all know, Pike's biggest problem has always been the lack of good documentation - since we have a way to change that now, why not do it?
marek
/ Brevbäraren