[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| RE: [wtp-dev] FW: Arrays vs. Collections in new API | 
No, I 
think we're primarily interested in "future proofing" the 
api.
Yes, 
we lose the strong typing offered by arrays in the short term, but we gain 
binary compatibility when we are finally allowed to convert to 
generics.
 
Except 
for the most memory sensitive situations (and in fact I think 
Konstantin actually found that he was using more memory implementing an array 
based api), I believe that most people will be adopting generics in the 
near future.
 
Once 
you've tasted the generics koolaid, it's really painful to encounter 
an array based api :-)
 
-Ted
  
Thanks for "netting 
  this out", Konstantin. 
Its a good 
  question, and a good time to ask, since normally, I think, Arrays are 
  preferred over Collections (for performance reasons), 
but as mentioned in the longer append, returning 
  immutable collections is a good way to improve thread safety. 
(I assume it the thread safety you're primarily 
  interested in?) 
I doubt we could 
  find or agree on a "whole WTP approach" so if you know of any specific cases 
  or areas, you might 
point those out in 
  feature requests with some assessment of impact, performance JUnits, etc. 
  
Thanks for raising this. 
  
  
    
    
      | "Konstantin 
        Komissarchik" <kosta@xxxxxxx> Sent by: wtp-dev-bounces@xxxxxxxxxxx
 08/16/2005 03:28 PM 
         
          
          
            | Please respond 
              to"General discussion of project-wide or architectural 
              issues."
 |  
 | 
          
          
            | To | "General discussion of 
              project-wide or architectural issues." 
              <wtp-dev@xxxxxxxxxxx> |  
            | cc |  |  
            | Subject | RE: [wtp-dev] FW: 
              Arrays vs. Collections in new API |  
 
 | 
No, we are not proposing to move to Java 5.0 for the 1.0 
  release. What the conversation was about and what we would like to propose to 
  WTP as a whole is to consider moving to using unparameterized Collections in 
  the API for the 1.0 release. Then, when platform and WTP moves to Java 5.0 
  (3.2/1.5?), the APIs can be changed to use parameterized collections without 
  breaking binary compatibility. 
  
Thoughts? 
  
- 
  Konstantin 
  
  
  
  
From: wtp-dev-bounces@xxxxxxxxxxx 
  [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of David M 
  Williams
Sent: Tuesday, August 16, 2005 11:44 AM
To: 
  General discussion of project-wide or architectural issues.
Subject: 
  Re: [wtp-dev] FW: Arrays vs. Collections in new API 
  
This was interesting ... but to be clear, our 1.0 will be on 
  Eclipse 3.1.1 and, I'm guessing, when 
Jim said "in the fall they will 
  start to use Java 5.0" I suspect he meant for the 3.2 stream. 
Are you suggesting we standardize on Java 5.0 for our API and 1.0 
  release? 
If so ... seems like a huge step, to me. 
So ... just thought I'd ask for clarification ... maybe you were 
  just sharing 
an interesting discussion? 
>Jim des Rivieres 
  wrote up this helpful response to an API question we had, and 
>agreed 
  to let me forward it to the list.  Something to consider as we finalize 
  api for 1.0.
> 
>-Ted_______________________________________________
wtp-dev mailing 
  list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev