commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <benerit...@gmail.com>
Subject Re: [all] Does this break binary compatibility?
Date Mon, 09 Jul 2012 07:26:16 GMT
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)	-	Breaks compatibility

Can anyone verify that?

Regards,
Benedikt

2012/7/9 S├ębastien Brisard <sebastien.brisard@m4x.org>:
> 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 the same paradigm. In other words, I would like to
> change the signature to
> public RealVector unitize()
> this method now returning this.
>
> Question is: does this break binary compatibility? Although clirr
> reports an error, I fail to see how this change can cause any problem.
>
> Thanks in advance for your advice,
> S├ębastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message