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 am new at learning Java. I really need your help. Actually, I know it is easy for most of you, but I just really lost, can not figure that out. I am supposed to write a code which The program asks the user to enter two integers. Then it asks three questions: what's the product of the two integers, what's the quotient of the two integers, and what's the remainder of the division of the two integers. It inputs the answers to each of the question from the user, tells the user whether the answer was correct or worng, and finally prints a message that depends on how many correct answers the user provided.
I did the beginning, but I can not see the logic of if statements. The program supposed to say wrong or write in accordance with the users' answer. I can not provide wrong or right. How can I fix it? Thank you so much
There may be other issues with the code, but these few lines are problematic:
"score1" is an int - you can't compare it with a boolean (which is what "true" is); you can only compare it to another int. Also, the value of score1 is changed by two successive statements, so the first value (a*b) will be lost. I think you mean something like this:
int score1 = in.nextInt();
if (score1 != a *b)
As an aside, this forum is specifically for question about threads and synchronization (see its title). I'll move it to a more appropriate forum.
To elaborate on Campbell's last note... writing this is unnecessary:
all you have to write is
assuming that 'something' is a boolean (and if it's not, you'll get an error). The problem with writing it out is that if you forget one of the two '=' characters, you ASSIGN the literal value to your variable, and the if condition will ALWAYS evaluate to your literal.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Joined: Oct 13, 2005
fred rosenberger wrote:To elaborate on Campbell's last note... writing this is unnecessary:
. . .
And to elaborate on Fred's last note . . . If you want something to be false you never writeAlways write