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.
I would just remind you that array length must be set at the time of instantiation. For example...
The array's elements can be automatically initialized (null for object references, or zero for primitive values), but you need to instantiate the array first -- otherwise the array reference itself will be automatically initialized to null, and trying to access a particular element will result in the null pointer exception you're seeing now. [ February 08, 2005: Message edited by: marc weber ]
"We're kind of on the level of crossword puzzle writers... And no one ever goes to them and gives them an award." ~Joe Strummer sscce.org
Note: This problem has nothing to do with the array references being static.
As static declarations, they will automatically initialize at class load time. If they were non-static, they would automatically initialize upon instantiation. But in both cases, the array references will initialize to null, and you'll get an exception when you try to access an element. [ February 08, 2005: Message edited by: marc weber ]