On Thu, Feb 18, 2010 at 13:28, Fabrizio Giudici <[email protected]> wrote: > But the point is that now I'd like to extend API compatibiltity checks > to a large number of my projects, and before escalating I'd like to > check whether there are other tools for the same job, just to have a > better awareness.
Since on Java I read more about such compatibility issues. While on Windows development the COM components could be compiled with binary compatibility basically meaning that compiler threw an error if public interfaces were changed. I think, if refactoring wouldn't be so easy (thanks to the powerful IDEs) and people would think more first before designing and changing APIs, that would not be such an issue. Apart from the tools (I don't know if there are some - so in reality I am off-topic with my thoughts), I wonder why there are no appropriate conventions (or at least I can't see any) similar to other conventions in the Java world (e.g. starting variables with lowercase and classes with uppercase etc). E.g. A change in major version of a class could mean incompatibility - something like this. -- Martin Wildam -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
