Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ariel,
is there already a general agreement about when API changes will be allowed?
In my understanding, there was no definitive answer to this question in
the thread which discussed it. The general consensus seemed to be
towards "change anything you like (as long as it's reasonable) in a
major release". In my opinion, this /perhaps/ is somewhat too generous
for a major release, and /definitely/ too restrictive for all
intermediate releases.
Well, I think I'll challenge that rule sooner or later, I have a lot of
small changes to start with :). For instance, I'd like to take all those
awt/form services which effectively describe *implementations* in OOo,
and make all the "optional" properties added over the years
non-optional, to match reality.
mmh, i would also think about converting the services in multiple
inheritance interfaces with type safe get/set function or even
attributes. If you provide also your own forms specific context it would
be quite easy to use the new create functions directly.
When we do API changes we should always check if it make sense or is
possible to migrate to multiple inheritance interfaces without
reimplementing everything new. Well i know it depends heavily on the
underlying implementation but it's worse to check it.
You are the expert in this area and knows better if possible or not.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
