This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
It's because of this line: "ArrayList b = a;". Notice that on the next line: "ArrayList<Bus> c = (ArrayList<Bus> )b;" you get an unchecked warning. That's because the compiler no longer knows the exact type of the objects in the array b. It's (to the compiler) just an array of objects. It allows the cast but emits the nonchecked warning so you are aware that it could cause a runtime ClassCastException later. That's would happen if the for loop was changed to:
Thanks Barry, that's really helpful. I'm taking the exam in the next 2 days, but still not sure if I'm really well prepared or just give it ago. scored around 50-80% (just couple of times though) on various mock exams.
Originally posted by Barry Gaunt: It's because of this line: "ArrayList b = a;"
just wonder and I think this will be useful, why compiler does Not give us a warning when we assign typed collection to "plain" collection?
Joined: Aug 03, 2002
The code: does not generate a warning because it is 100% OK to do it. Variable b only needs an ArrayList of some kind of objects assigned to it. They do not even have to be the same type, but here we are in fact assigning an ArrayList of objects that are all the same - Cars. So at this point there is nothing for the compiler to complain about. [ January 22, 2007: Message edited by: Barry Gaunt ]