Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Objectteams » Binary (in)compatibility?
Binary (in)compatibility? [message #567589] Thu, 14 January 2010 19:19
Stephan Herrmann is currently offline Stephan HerrmannFriend
Messages: 1843
Registered: July 2009
Senior Member
I've just started working on a ticket that will introduce a binary
incompatibility. If this feature will be included in the next
milestone this will imply, that old OT/J .class files cannot
be used with the new runtime environment.

By this post I'm asking for feedback how big a problem such
incompatibility would impose on everybody. At all times, re-compiling
existing sources will suffice, since source-level compatibility is
not affected.

This is about :
"Allow teams extending a non-team class".
I'm introducing a new interfaces org.objectteams.ITeam, which
will be used in many locations that until now use the class
org.objectteams.Team. Specifically, if a team class extends
a non-team class, the compiler will implicitly insert
"implements org.objectteams.ITeam" instead of
"extends org.objectteams.Team".

Several internal, generated methods currently mention class Team,
which will be changed, too. Thus the incompatibility.

So, please speak up if you're seeing problems with this change.
I would have to try hard to add a compatibility mode or back out
the current work.

Previous Topic:Role migration - is it really needed?
Next Topic:Binary (in)compatibility?
Goto Forum:

Current Time: Mon Jan 17 15:23:06 GMT 2022

Powered by FUDForum. Page generated in 0.01983 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top