Fairly often (while backward incompatible changes are of course rare). It's much more common that I improve old functions in one way or the other than that I add new functions.
And if you change them, then you can mark the version where it changed in the argument description - which you have to modify anyway.
The only way to do it with negligible effort is to copy the old description and then update one of the copies. That's however a sure way of making the documentation unreadable and I definitely don't want the current docs cluttered up with compatibility stuff. That can be a set of notes at the bottom that are easy to skip, else I think it's better left out completely.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-02-07 01:54: Subject: Re: API version tagging
On Fri, Feb 07, 2003 at 01:40:01AM +0100, Martin Stjernholm, Roxen IS @ Pike developers forum scribbled:
It's not just new functions. You have to add blurbs about added arguments too and other changed semantics etc. If it should remain readable it is a bit of extra work, in my experience.
How often do you change arguments, though? And if you change them, then you can mark the version where it changed in the argument description - which you have to modify anyway.
marek
/ Brevbäraren