On Sunday, April 25, 2004, at 03:47 pm, Stephen Kellett wrote:If you needed to change an API, you'd create an Ex() version of it, ala Microsoft
Yuk. Please do not fall prey to the habits of an 800-lb gorilla. Microsoft's bad
design habits should not be relied upon as any sort of "standard practice."
No, that *is* precisely good practice.
Have you never written a library of routines for use in several programs?
Then for program 7, you improve on of the routines in the library by altering it. Maybe you even fix a bug in it. Then later you come back to change Program 3: maybe you even simply recompile it without improvement. But it's broken because the library has changed.
Nope: once frozen in the library, NEVER change it. Always add a new API with a new name.
Common sense.
-- Bernard Hill Braeburn Software Author of Music Publisher system Music Software written by musicians for musicians http://www.braeburn.co.uk Selkirk, Scotland
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
