Hello Angus, > No, it's the job of the person introducing the changes to make sure the > component is backward compatible, and if not, document VERY CLEARLY at > the top of the code any implications of the changes, not just in this > mailing list. And to clearly mark and date and changes.
Agree, but impossible to test / know all implementations. A good example is a programmer that use a component version wich have a bug and he did a workaround for it for his application. It is even possible that the programmer in question did not know that it was a bug because he do not know the protocol. This is always a known problem with 'living' code. You have to maintain older code and 'bang' some bug introduced :( I think Francois does real hard do his best for backward compatibility and we cannot say that for every component / library, even not some where you pay hard dollars for. --- Rgds, Wilfried http://www.mestdagh.biz -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
