| Binary Compatibility [message #55386] |
Thu, 16 January 2003 15:07  |
Eclipse User |
|
|
|
On the GEF Overview Page the following statement is made:
The API is stable, but we have not claimed binary compatibility with future
major releases like the Eclipse Platform.
Does anyone know if we can *assume* that binary compatibility will be
maintained after the initial
release of GEF?
Thanks, MM
|
|
|
| Re: Binary Compatibility [message #58872 is a reply to message #55386] |
Tue, 28 January 2003 15:43  |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
"Mike McGowan" <mike.mcgowan@lawson.com> wrote in message
news:b072m4$nb7$1@rogue.oti.com...
> On the GEF Overview Page the following statement is made:
>
> The API is stable, but we have not claimed binary compatibility with
future
> major releases like the Eclipse Platform.
>
> Does anyone know if we can *assume* that binary compatibility will be
> maintained after the initial
> release of GEF?
The answer is hopefully. There is optimistic binary compatibility, which
says that we can create a new API method and hopefully you haven't already
created the same method in your subclasses. This is probably what we will
shoot for. For example, if Eclipse adds a new method to
MultiPageEditorPart, and I already that method in my subclass, I'm broken.
I don't think "real" binary compatibility exists. That would mean that no
API could be added to "framework" classes such as Figure.
Eclipse has had blatant breaks in the past, such as adding dispose() to
IEditorActionBarContributor in 2.0. Clearly all implementors of the
interface were broken. I keep reading things that say "Eclipse X.x will be
binary compatible unless otherwise noted", but I can never find where the
exceptions are noted.
|
|
|
Powered by
FUDForum. Page generated in 0.07635 seconds
Home