[all] Does this break binary compatibility?

2012-07-09 Thread Sébastien Brisard
All, in Commons-Math, class RealVector has a method unitize() which divides each component of this by the norm. The vector is changed in place. The current signature of this method is public void unitize() Most methods in class RealVector implement a fluent API. I would like unitize() to follow

Re: [all] Does this break binary compatibility?

2012-07-09 Thread Benedikt Ritter
Hi Sebastien, have a look at: http://wiki.eclipse.org/Evolving_Java-based_APIs http://wiki.eclipse.org/Evolving_Java-based_APIs_2 http://wiki.eclipse.org/Evolving_Java-based_APIs_3 In section Evolving API classes - API methods and constructors it says: Change result type (including void) -

Re: [all] Does this break binary compatibility?

2012-07-09 Thread Julien Aymé
In fact, changing the return type does break binary compatibility (binary compatibility is different from source compatibility), since the return type of a method is part of is java signature. This means that if someone would want to use the new jar (with changed return type) as a drop-in

Re: [all] Does this break binary compatibility?

2012-07-09 Thread Sébastien Brisard
Hi, In fact, changing the return type does break binary compatibility (binary compatibility is different from source compatibility), since the return type of a method is part of is java signature. This means that if someone would want to use the new jar (with changed return type) as a