🚀 go-pugleaf

Raul Lorenzo wrote:
> Hello,
> 
> I have this piece of code:
> 
> ArrayList<Element> children = new ArrayList<Element>();
> children.addAll(current.getOwnedElement());
> 
> What do I need to add to second line to remove the warning?

What warning are you getting?

Oh, you violated rule #0 -- NEVER put valuable information
in the subject line!

What is the declared return type for "current.getOwnedElement()"?

Collection<Element>?

as in ...

public class GenericsTest {
   public GenericsTest() {
   }

   public static void main(String[] args) {
     GenericsTest test = new GenericsTest();
     Current current = new Current();
     ArrayList<Element> children = new ArrayList<Element>();
     children.addAll(current.getOwnedElement());
   }

   public static class Current {
     public Collection<Element> getOwnedElement() {
       return null;
     }
   }
}

Your choice of names seems odd: "ownedElement" doesn't
connote a collection required by "addAll".  "ownedElements"
would seem to be more appropriate.


-- 


Paul Furbacher (TeamB)

   Save time, search the archives:
        http://info.borland.com/newsgroups/ngsearch.html

   Is it in Joi Ellis's Faq-O-Matic?
        http://www.visi.com/~gyles19/fom-serve/cache/1.html

   Finally, please send responses to the newsgroup only.
   That means, do not send email directly to me.
   Thank you.

Paul Furbacher [TeamB] escribi�:
> Raul Lorenzo wrote:
>> Hello,
>>
>> I have this piece of code:
>>
>> ArrayList<Element> children = new ArrayList<Element>();
>> children.addAll(current.getOwnedElement());
>>
>> What do I need to add to second line to remove the warning?
> 
> What warning are you getting?
> 
> Oh, you violated rule #0 -- NEVER put valuable information
> in the subject line!
Sorry about that, I wrote a clear subject, but I should repeat the
information in body message.
> 
> What is the declared return type for "current.getOwnedElement()"?
> 
> Collection<Element>?
It returns Collection simply.
> 
> Your choice of names seems odd: "ownedElement" doesn't
> connote a collection required by "addAll".  "ownedElements"
> would seem to be more appropriate.
It isn�t my choice, that method belongs to MagicDraw OpenAPI, so I
couldn�t change it.
current is a kind of container which could have different kind of
elements, and those elements are returned by getOwnedElement().

Raul Lorenzo wrote:

> [the] method belongs to MagicDraw OpenAPI, so I
> couldn�t change it.
> current is a kind of container which could have different kind of
> elements, and those elements are returned by getOwnedElement().

In that case, one alternative would be to add the annotation

   @SuppressWarning("unchecked")

to stifle the warning.


-- 


Paul Furbacher (TeamB)

   Save time, search the archives:
        http://info.borland.com/newsgroups/ngsearch.html

   Is it in Joi Ellis's Faq-O-Matic?
        http://www.visi.com/~gyles19/fom-serve/cache/1.html

   Finally, please send responses to the newsgroup only.
   That means, do not send email directly to me.
   Thank you.

Paul Furbacher [TeamB] wrote:
> In that case, one alternative would be to add the annotation
> 
>   @SuppressWarning("unchecked")
> 
> to stifle the warning.

This doesn't work in the JDK provided with JB2006.  You would need to 
upgrade to the latest JDK1.5 Update 6 in order to get support for this. 
  You would also probably need to enable "project javac" as the Java 
compiler for the project.

I haven't actually tested that this works in update 6, but the Sun Bug 
Parade implies that it should.

Fun hypothetical question to pass some time with today: WTF was the 
point of implementing a SuppressWarnings annotation but not actually 
doing anything with it in the compiler until 6 updates down the line? 
AFAIK Eclipse has supported it for a long while.  Was this some kind of 
backdoor nod to Eclipse from Sun?

-- 
Gillmer J. Derge [TeamB]