Home » Language IDEs » Java Development Tools (JDT) » [ANN] JDT 1.5 update available - Cheetah 03
| [ANN] JDT 1.5 update available - Cheetah 03 [message #154674] |
Fri, 16 April 2004 12:47  |
Eclipse User |
|
|
|
Dear 1.5 fans,
The Cheetah is now able to digest generic methods and perform type
inference.
It also recognizes the Object.getClass() method and perform adequate
substitutions (see 57784).
Additionally, the new Cheetah does address the following defects:
58715 [1.5] The return type is incompatible
58631 [1.5] Cycle in hierarchy no longer detected
57784 [1.5] Object.getClass() need to be treated special ?
57784 [1.5] Errors using Arrays.asList(T [])
58461 [1.5] java.lang.VerifyError from enhanced for loop
53036 Incorrect highlighting for type problem in qualified type name
Please retrieve Cheetah03 from our update site, and find more info at:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- core-home/r3.0/main.html#updates
Several people have reported installation issues. These are bugs in Eclipse
itself.
As a workaround, when installing the Cheetah, the platform will usually
crash during restart;
simply exit and restart once more. It should work ok from thereon, don't try
to do anything
before you do so.
As usual, if you find issues with it (and yes, you will <g>), then please
enter a bug report against JDT Core, where you prefix the problem title
with "[1.5]" so we can easily identify these issues; and please also
mention the version of the Cheetah you are riding (see Eclipse help about
plug-in details: e.g. Eclipse Java Development Tools Core 3.0.0.cheetah03).
We are now looking at covariance & bridge method support.
The JDT Core team
|
|
| | |
| Re: [ANN] JDT 1.5 update available - Cheetah 03 [message #154713 is a reply to message #154674] |
Fri, 16 April 2004 15:07  |
| Eclipse User |
|
|
|
Hey Philippe,
I don't know if these are existing bugs, or if these are known features
holes with Cheetah 3 - but so far here are a couple things that immediately
broke when I switched to the 1.5 compliance level:
- Collections.singletonList(Object) - I couldn't find any way to get this
method to work, no matter what I did.
- Copy Constructors - new [Collection]([Collection of same type]);
-- e.g.:
new HashMap<String, String>(new HashMap<String, String>());
new ArrayList<String>(new ArrayList<String>());
Are these things that are known to be a problem/missing feature, am I doing
something wrong, or should I file a bug report? I am no generics wizard, but
I didn't expect to have any compilation ERRORS after switching (I expected a
ton of warnings however).
As a sidebar, does anyone know how I can enforce type-safety using the empty
lists from the Collection class? (e.g.: Collections.emptyList()).
Thanks for your hard work on the 1.5 features, I know a lot of us appreciate
it.
R.J.
"Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
news:c5p2c4$pau$1@eclipse.org...
> Dear 1.5 fans,
>
> The Cheetah is now able to digest generic methods and perform type
> inference.
> It also recognizes the Object.getClass() method and perform adequate
> substitutions (see 57784).
>
> Additionally, the new Cheetah does address the following defects:
> 58715 [1.5] The return type is incompatible
> 58631 [1.5] Cycle in hierarchy no longer detected
> 57784 [1.5] Object.getClass() need to be treated special ?
> 57784 [1.5] Errors using Arrays.asList(T [])
> 58461 [1.5] java.lang.VerifyError from enhanced for loop
> 53036 Incorrect highlighting for type problem in qualified type name
>
> Please retrieve Cheetah03 from our update site, and find more info at:
>
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- core-home/r3.0/main.html#updates
>
> Several people have reported installation issues. These are bugs in
Eclipse
> itself.
> As a workaround, when installing the Cheetah, the platform will usually
> crash during restart;
> simply exit and restart once more. It should work ok from thereon, don't
try
> to do anything
> before you do so.
>
> As usual, if you find issues with it (and yes, you will <g>), then please
> enter a bug report against JDT Core, where you prefix the problem title
> with "[1.5]" so we can easily identify these issues; and please also
> mention the version of the Cheetah you are riding (see Eclipse help about
> plug-in details: e.g. Eclipse Java Development Tools Core
3.0.0.cheetah03).
>
> We are now looking at covariance & bridge method support.
> The JDT Core team
>
>
|
|
|
| Re: [ANN] JDT 1.5 update available - Cheetah 03 [message #154721 is a reply to message #154713] |
Fri, 16 April 2004 15:52 |
| Eclipse User |
|
|
|
Remember the Cheetah isn't done yet. I would certainly not declare success
yet on generics front.
Could you enter a bug against JDT Core about this issue, we will investigate
it (with "[1.5]" prefix in title) ?
I am suspecting a few holes in our support, and many things which we don't
yet digest, like covariance.
"R.J. Lorimer" <rjlorimer@coffee-bytes.com> wrote in message
news:c5pai6$40k$1@eclipse.org...
> Hey Philippe,
>
> I don't know if these are existing bugs, or if these are known features
> holes with Cheetah 3 - but so far here are a couple things that
immediately
> broke when I switched to the 1.5 compliance level:
>
> - Collections.singletonList(Object) - I couldn't find any way to get this
> method to work, no matter what I did.
>
> - Copy Constructors - new [Collection]([Collection of same type]);
>
> -- e.g.:
>
> new HashMap<String, String>(new HashMap<String, String>());
>
> new ArrayList<String>(new ArrayList<String>());
>
> Are these things that are known to be a problem/missing feature, am I
doing
> something wrong, or should I file a bug report? I am no generics wizard,
but
> I didn't expect to have any compilation ERRORS after switching (I expected
a
> ton of warnings however).
>
> As a sidebar, does anyone know how I can enforce type-safety using the
empty
> lists from the Collection class? (e.g.: Collections.emptyList()).
>
> Thanks for your hard work on the 1.5 features, I know a lot of us
appreciate
> it.
>
> R.J.
>
> "Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
> news:c5p2c4$pau$1@eclipse.org...
> > Dear 1.5 fans,
> >
> > The Cheetah is now able to digest generic methods and perform type
> > inference.
> > It also recognizes the Object.getClass() method and perform adequate
> > substitutions (see 57784).
> >
> > Additionally, the new Cheetah does address the following defects:
> > 58715 [1.5] The return type is incompatible
> > 58631 [1.5] Cycle in hierarchy no longer detected
> > 57784 [1.5] Object.getClass() need to be treated special ?
> > 57784 [1.5] Errors using Arrays.asList(T [])
> > 58461 [1.5] java.lang.VerifyError from enhanced for loop
> > 53036 Incorrect highlighting for type problem in qualified type name
> >
> > Please retrieve Cheetah03 from our update site, and find more info at:
> >
>
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- core-home/r3.0/main.html#updates
> >
> > Several people have reported installation issues. These are bugs in
> Eclipse
> > itself.
> > As a workaround, when installing the Cheetah, the platform will usually
> > crash during restart;
> > simply exit and restart once more. It should work ok from thereon, don't
> try
> > to do anything
> > before you do so.
> >
> > As usual, if you find issues with it (and yes, you will <g>), then
please
> > enter a bug report against JDT Core, where you prefix the problem title
> > with "[1.5]" so we can easily identify these issues; and please also
> > mention the version of the Cheetah you are riding (see Eclipse help
about
> > plug-in details: e.g. Eclipse Java Development Tools Core
> 3.0.0.cheetah03).
> >
> > We are now looking at covariance & bridge method support.
> > The JDT Core team
> >
> >
>
>
|
|
|
| Re: [ANN] JDT 1.5 update available - Cheetah 03 [message #154759 is a reply to message #154721] |
Fri, 16 April 2004 18:18 |
| Eclipse User |
|
|
|
Understood fully! Bug has been entered:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=58950
I don't want to give the impression I expect Cheetah to be complete; I just
wanted to make sure that I wasn't echoing anyone else needlessly. I
recognize based on what I've seen in mailing lists etc that there is still
somewhat of a lack of compliance testing available so my main goal was to
just bring some of the holes to your attention; there is so many scenarios
that have to be covered after all.
If I find anything else I will be sure to bring it to your attention -
thanks!
"Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
news:c5pd7p$7d9$1@eclipse.org...
> Remember the Cheetah isn't done yet. I would certainly not declare success
> yet on generics front.
> Could you enter a bug against JDT Core about this issue, we will
investigate
> it (with "[1.5]" prefix in title) ?
>
> I am suspecting a few holes in our support, and many things which we don't
> yet digest, like covariance.
>
> "R.J. Lorimer" <rjlorimer@coffee-bytes.com> wrote in message
> news:c5pai6$40k$1@eclipse.org...
> > Hey Philippe,
> >
> > I don't know if these are existing bugs, or if these are known features
> > holes with Cheetah 3 - but so far here are a couple things that
> immediately
> > broke when I switched to the 1.5 compliance level:
> >
> > - Collections.singletonList(Object) - I couldn't find any way to get
this
> > method to work, no matter what I did.
> >
> > - Copy Constructors - new [Collection]([Collection of same type]);
> >
> > -- e.g.:
> >
> > new HashMap<String, String>(new HashMap<String, String>());
> >
> > new ArrayList<String>(new ArrayList<String>());
> >
> > Are these things that are known to be a problem/missing feature, am I
> doing
> > something wrong, or should I file a bug report? I am no generics wizard,
> but
> > I didn't expect to have any compilation ERRORS after switching (I
expected
> a
> > ton of warnings however).
> >
> > As a sidebar, does anyone know how I can enforce type-safety using the
> empty
> > lists from the Collection class? (e.g.: Collections.emptyList()).
> >
> > Thanks for your hard work on the 1.5 features, I know a lot of us
> appreciate
> > it.
> >
> > R.J.
> >
> > "Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
> > news:c5p2c4$pau$1@eclipse.org...
> > > Dear 1.5 fans,
> > >
> > > The Cheetah is now able to digest generic methods and perform type
> > > inference.
> > > It also recognizes the Object.getClass() method and perform adequate
> > > substitutions (see 57784).
> > >
> > > Additionally, the new Cheetah does address the following defects:
> > > 58715 [1.5] The return type is incompatible
> > > 58631 [1.5] Cycle in hierarchy no longer detected
> > > 57784 [1.5] Object.getClass() need to be treated special ?
> > > 57784 [1.5] Errors using Arrays.asList(T [])
> > > 58461 [1.5] java.lang.VerifyError from enhanced for loop
> > > 53036 Incorrect highlighting for type problem in qualified type name
> > >
> > > Please retrieve Cheetah03 from our update site, and find more info at:
> > >
> >
>
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- core-home/r3.0/main.html#updates
> > >
> > > Several people have reported installation issues. These are bugs in
> > Eclipse
> > > itself.
> > > As a workaround, when installing the Cheetah, the platform will
usually
> > > crash during restart;
> > > simply exit and restart once more. It should work ok from thereon,
don't
> > try
> > > to do anything
> > > before you do so.
> > >
> > > As usual, if you find issues with it (and yes, you will <g>), then
> please
> > > enter a bug report against JDT Core, where you prefix the problem
title
> > > with "[1.5]" so we can easily identify these issues; and please also
> > > mention the version of the Cheetah you are riding (see Eclipse help
> about
> > > plug-in details: e.g. Eclipse Java Development Tools Core
> > 3.0.0.cheetah03).
> > >
> > > We are now looking at covariance & bridge method support.
> > > The JDT Core team
> > >
> > >
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Sat May 10 12:32:58 EDT 2025
Powered by FUDForum. Page generated in 0.03306 seconds |
Home