[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cross-project-issues-dev] Java 1.5
|
You have my sympathy, Ed (and EMF team)! It seems like writing
"templatized" API is an order of magnitude harder than simply consuming it.
Probably another order of magnitude if you plan on making EClass itself
templatized, whatever that would mean.
You could probably spend half the release trying to figure out:
class Enum<E extends Enum<E>>
;-) ;-)
-Randy
Ed Merks
<merks@xxxxxxxxxx
> To
Sent by: Cross project issues
cross-project-iss <cross-project-issues-dev@eclipse.o
ues-dev-bounces@e rg>
clipse.org cc
Subject
10/05/2006 10:41 RE: [cross-project-issues-dev] Java
AM 1.5
Please respond to
Cross project
issues
<cross-project-is
sues-dev@eclipse.
org>
Doug,
EMF is in a bit of an odd position in that it provides and uses it own
runtime. So unlike the JDT, which can target any JVM and hence can support
Java 5.0 without using Java 5.0 itself, EMF must target its own runtime.
For example, org.eclipse.emf.common..util.EList which extends
java.util.List to add move methods needs to be templatized just as is List
itself and similarly the implementation class
org.eclipse.emf.common.util.BasicEList needs to be fully templatized. As
such, the org.eclipse.emf.common plugin will depend on Java 5.0 and since
all the rest of EMF depends on this, all the rest of EMF will be bound by
that decision; and of course we'll want to regenerate the Ecore API to
support Java 5.0. So EMF 3.0 will absolutely not run on a 1.4 VM (which is
why we are moving to EMF 3.0 rather than EMF 2.3, even though we hope to
provide a binary compatible runtime capable of running 2.2-based code
without recompilation). It's a huge undertaking for our tiny team, given
that there is little experience in this domain from which we can draw. I'm
finding that templatizing collection APIs is shockingly complicated (even
though using templatized APIs is usually rather simple and nice).
Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265 (t/l 969)
Doug Schaefer <DSchaefer@xxxxxxx>
Sent by:
cross-project-issues-dev-bounces@e To
clipse.org Cross project issues
<cross-project-issues-dev@
eclipse.org>
10/05/2006 10:27 AM cc
Subject
Please respond to RE:
Cross project issues [cross-project-issues-dev]
<cross-project-issues-dev@eclipse Java 1.5
.org>
Thanks, Ed. I was thinking more about the runtime for your plug-ins. Will
EMF 3.0 run on a 1.4 VM?
Doug Schaefer
QNX Software Systems
Eclipse CDT Project Lead
http://cdtdoug.blogspot.com
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Merks
Sent: Thursday, October 05, 2006 10:23 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Java 1.5
Doug,
Supporting and exploiting Java 5.0 is the main development item for EMF
3.0. We hope to make generating the 5.0 features optional and to ensure
that generated code can compile and run against the 2.2 EMF runtime so that
folks needing support for Java 1.4 will be able to achieve that.
Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265 (t/l 969)
Richard Gronback
<richard.gronback@xxxxxxxxxxx>
Sent by:
cross-project-issues-dev-bounces@e To
clipse.org Cross project issues
<cross-project-issues-dev@
eclipse.org>
10/05/2006 10:14 AM cc
Subject
Re:
[cross-project-issues-dev]
Java 1.5
Please respond to
Cross project issues
<cross-project-issues-dev@eclipse
.org>
GMF is using 1.5 language features for this release.
- Rich
On 10/5/06 10:13 AM, "Doug Schaefer" <DSchaefer@xxxxxxx> wrote:
Hey gang, I’m just wondering if any of the projects participating in Europa
are planning on dropping support for Java 1.4, i.e. are planning on using
Java 1.5 features.
Doug Schaefer
QNX Software Systems
Eclipse CDT Project Lead
http://cdtdoug.blogspot.com
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Richard C. Gronback
Borland Software Corporation
richard.gronback@xxxxxxxxxxx
+1 860 227 9215_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
