Talk:Java Programming/Collection

IMHO This needs attention. I'm not sure it can be fixed without a complete rewrite. It is not written well (must be someone for whom English is not their fist language?), and the structure is not good. There is some good content in there, and the person that wrote it probably does have a grasp on collections, but it needs some attention.

I have changed the status of this page to 25% . I will be rewriting some of the sections to provide the reader with delightful insights. Thanks for notifying the problem. Remember, do sign off whenever you add a comment with ~~~~. - Arunreginald 15:04, 2 November 2006 (UTC)Reply

I share the concern of the anonymous commentor. The article contains good information but unfortunately lacks a logical structure. Some suggestions in terms of content:

• Generics is mentioned but it should be made clear that you used to have the casting problems, not with generics. The way it is written now suggests that it's the problem when using generics.

I have fixed this point.

• More basic coding examples for each group including using generics.

I have added code.

• Explain about 'syncronized' earlier in the article instead of in the end. Since you use it extensively in the article, it's only confusing now if you don't know what it means.

I have added a section but this section needs to be completed.

• Separate the in depth info like the comparison troubles with sets.
• The package prefixes before each interface and implementation does not improve the readability of the article. Consider removing them or including them in a different manner.

I have used colors.

• The LinkList pointer bit should realy need some more explaination.
• Consider including a table like in 'The Java Tutorials - Collections' by Josh Bloch. This would provide a clear overview of the posibilities.
• Queue remain basically unexplained.
• Some questions people might have after reading the article that might need answering:
  • Should or shouldn't we still use the old style, i.e. not using generics in all cases?

It should be OK now.

• • If sets don't allow duplicates in the first place, why should we check if there's a duplicate ourselfs?
  • You talk about 'syncronized' and 'non-syncronized' as if it's something different then 'thread safe', is it?

Mentioned.

• • In examples like Collection coll2 = new HashSet(); you make coll2 of the type Collection. Why not make it HashSet instead? E.g. HashSet coll2 = new HashSet(); or Set coll2 = new HashSet(); even. Prodoc (talk) 08:53, 6 March 2009 (UTC)Reply

This point is explained in the page: It lets you switch from one implementation to another easily. Ftiercel (discuss • contribs) 02:44, 21 October 2012 (UTC)Reply

I notice that the navigation of this page is displaying the link for Java Aggregate classes but the Java Aggregate is not listed in the TOC. Shchung (discuss • contribs) 06:41, 17 September 2014 (UTC)Reply

I have renamed the chapter. Ftiercel (discuss • contribs) 12:58, 18 September 2014 (UTC)Reply