List

[java4amanda]

Hi all,


I was going through an article on list and i bumped on this line of code >>> List l = new ArrayList<Integer>(); , and when i tried running that code i get this error " incompatible type." Any idea??

Regards,
Shishir

[DarrylBurke]

You probably imported the wrong class.

db

[JosAH]

Hi all,


I was going through an article on list and i bumped on this line of code >>> List l = new ArrayList<Integer>(); , and when i tried running that code i get this error " incompatible type." Any idea??

That line is trying to assign a generic List<String> to a 'raw' list; the compiler warns against it.

kind regards,

Jos

[java4amanda]

no i used import java.util.*;

[Tolls]

If you are getting an "incompatible types" error on that line then the compiler is finding another List or ArrayList class in your classpath.
It is either a class you have created or one you have imported.

The only thing (assuming you do not have any extraneous List/ArrayList classes lying around) you should get from that line is a generics warning.

[java4amanda]

thanks!!

[Tolls]

And the solution was?

[DarrylBurke]

The solution was: take what you can get from a forum, never give anything back.

db

[JosAH]

The solution was: take what you can get from a forum, never give anything back.

Here are some more tips:

1) Crosspost as much as possible but don't tell anyone; posting is like fishing: the more bait you throw in the more answers you'll get.
2) Use txt speak or even better: combine it with sms speak; people don't like to read complete words.
3) Don't post your code and if you do, make sure it's uncompilable and don't add any code tags; if it were hard to write it should be hard to read.
4) Add as many links to vague sites as possible; it makes people curious.
5) Include the original assignment text as .pdf files.
6) Bump your thread every fifteen minutes or so; that'll wake up the lazy moderators.
7) Don't thank anyone for their answers; it's their duty to supply answers.
8) It's best to add your question to an old, long dead thread. New threads are expensive.
9) Supply your own interpretation to compilation errors (e.g. "the damn thing threw some stupid error at me"); the original messages as too vague.
10) Always use lower case letters in posts and no punctuation. If possible (not always) leave in some spelling mistakes because we all know how hard it is to double check your own posts.


kind regards,

Jos ;-)

[lannie1980]

lol

10) Always use lower case letters in posts and no punctuation. If possible (not always) leave in some spelling mistakes because we all know how hard it is to double check your own posts.

Best Regards

[JosAH]

lol

10) Always use lower case letters in posts and no punctuation. If possible (not always) leave in some spelling mistakes because we all know how hard it is to double check your own posts.

Best Regards

Very good; I added it to the list; maybe we can make it the canonical list of forum poster tips ;-)

kind regards,

Jos

[DarrylBurke]

3) Don't post your code and if you do, don't add any code tags; if it were hard to write it should be hard to read.

3) Don't post your code and if you do, make sure it's uncompilable and don't add any code tags; if it were hard to write it should be hard to read.

Added a phrase.

db

[JosAH]

3) Don't post your code and if you do, make sure it's uncompilable and don't add any code tags; if it were hard to write it should be hard to read.
Added a phrase.

Also a very good addition (added to the list).

kind regards,

Jos

[lannie1980]

get it stickied lol ;p