[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
On 05.03.2009 17:43, Sven Efftinge wrote:
On Mar 5, 2009, at 5:15 PM, Heiko Behrens wrote:
In the paragraph about the stable annotation you state: "This is
because we might want to add additional methods to those interfaces."
What is the meaning of "stable" than? Existing methods won't be
removed? Existing methods won't be changed regarding their signature?
Stable in the sense, that if you implement the interface as well as
subclassing the abstract class, our changes won't break your code.
That is, if you use it that way it remains stable.
Does this makes sense?
It sure does, but maybe we should be more clear about what this actually
means. From my viewpoint, this means:
- No methods removed
- No signature changes
- No precondition strengthening i.e. postcondition weakening
- No class invariant strengthening
Correct?
Regards,
Patrick
--
Patrick Schönbach
Software Architect
PGP public key available. Key ID: 0B7DDE39
Or email to pgp@xxxxxxxxxxxxx with subject 'pschoenb'.
Fingerprint: BE80 0E7E B68E CE99 623C 902D 62A6 806A 0B7D DE39
web: http://www.itemis.de
mail: schoenbach@xxxxxxxxx
xing: https://www.xing.com/profile/Patrick_Schoenbach
itemis AG
Schauenburgerstraße 116
24118 Kiel
Germany
Rechtlicher Hinweis:
Amtsgericht Dortmund, HRB 20621
Vorstand: Wolfgang Neuhaus, Jens Wagener, Dr. Georg Pietrek
Aufsichtsrat: Dr. Burkhard Igel(Vors.), Stephan Grollmann, Michael Neuhaus
