Java's arrays are "typed" - you declare them to contain a particular type of primitive, or a particular type of object (which also enables them to contain any object type which is extended from that declared type).

But, when you go beyond arrays and use the more flexible utility classes such as ArrayLists, Vectors, HashTables, etc, you are declaring a container that can hold any sort of object. So:
  ArrayList Allwords = new ArrayList();
and you "worry" the Java Compiler:
  [trainee@easterton cj]$ javac Utildemo.java
  Note: Utildemo.java uses unchecked or unsafe operations.
  Note: Recompile with -Xlint:unchecked for details.
  [trainee@easterton cj]$

You probably won't want to have this warning message crop up on every future compile (and, let's face it, Java is a real "maiden aunt" of a language when it comes to checking), so let's add in a request to make the checks in the declaration:
  ArrayList<String> Allwords = new ArrayList<String>();
(written 2010-04-23)

 J715 - Putting the Java Language Together
  [836] Build on what you already have with OO - (2006-08-17)
  [1181] Good Programming practise - where to initialise variables - (2007-05-09)
  [4326] Learning to program - comments, documentation and test code - (2014-11-22)
  [4430] The spirit of Java - delegating to classes - (2015-02-18)

Back to for and foreach in Java

Previous and next or Horse's mouth home

Forward to Perl Course FAQ

Melksham Scouts
What is all this SESSION stuff about? (PHP)
Improving your function calls (APIs) - General and PHP
Perl Course FAQ
Type checking, Java arrays and collections
for and foreach in Java
Travel Troubles and Jesus again
Asking about Jesus
Training Courses - time of change
Bird Watching on the Melksham Avon