Win a copy of Soft Skills: The software developer's life manual this week in the Jobs Discussion forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Hum, what's wrong here?

 
Jesse Crockett
Ranch Hand
Posts: 129
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is the output:




 
Ulf Dittmer
Rancher
Pie
Posts: 42966
73
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I haven't tried to use Scanner with System.in, but my guess would be that the call to nextInt expects a number to be available already, and since there is none, it throws an exception. In other words, the call doesn't wait until there is an int. Have a look at the hasNextInt method to see whether there actually is an int available.

And please UseAMeaningfulSubjectLine
[ January 13, 2007: Message edited by: Ulf Dittmer ]
 
Jim Yingst
Wanderer
Sheriff
Posts: 18671
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In general, nextInt() would block waiting for new input. The problem here is that System.in has already been closed, near the top of the method. Closing the scanner also closes the stream it's wrapped around. Once it's been closed, you can't reopen it. So when you later create a new Scanner wrapped around System.in, it can't possibly read anything - hence, the error you've gotten.

If you want to use System.in more than once, you need to create a single Scanner for reading System.in, and keep using it. Don't close it until you're really done with it, and don't try to create a new one.
 
Jesse Crockett
Ranch Hand
Posts: 129
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic