StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19371945
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-15T01:35:18.400
FavoriteCount
0
LastActivityDate
2013-10-15T01:35:18.400
LastEditDate
LastEditorUserId
0
OwnerUserId
415727
ParentId
19371534
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Your program has a Java syntax error, for which the compiler complains, and a more subtle logical error which is pretty common even among experienced programmers across the entire C/C++/C#/Java family. The syntax error is that the kind of for that you used needs the you specify a collection after the colon; or, more correctly, an object of a type which implements interface Iterable. Interfaces define a contract that authorizes the compiler to perform certain operations on the instances of a class which implement the interface. So, the compiler will handle iteration over a variable only if the variable is Iterable. Since in your case rolls is of type int (and hence is not even a class) and int is not Iterable, you get the error. You iterate on integers using the classic for, which is supported pretty much with no differences in C, C++, C# and Java. <pre><code>for (int num1 = 0; num1 < rolls; num1 = num1 + 1) /* A single statement (body) */; </code></pre> This statements means: repeat the body, that is the single statement mentioned after the for (...), exactly rolls times. More correctly, it implements the following algorithm: <pre><code>A. Initialize num1 to 0 B. Is num1 lesser than rolls? If yes, execute the body, increment num1 and go back to B If not, go to the first instruction after the **for** </code></pre> Now, the second problem; this could happen with both flavors of the for, but it is unlikely to go unnoticed with the Iterable flavor. You most likely don't want a semicolon right after the for statement; here's why. A design decision for C and all languages with C-like syntax, like Java, is that in most places where you want to insert one or more statements, only one statement can actually be inserted. The for cycle can handle only a single instruction in its body, and it's going to be the one after the ), disregarding indentation and coding style. Consider the following two for cycles: <pre><code>// Prints numbers from 0 to 9 int x = 0; for (x = 0; x < 10; x = x + 1) System.out.println(x); // Prints 10 int y = 0; for (y = 0; y < 10; y = y + 1); System.out.println(y); </code></pre> They look alike, but the effect of the first code fragment is printing the numbers from 0 to 9, while the effect of the second is printing 10. The reason is that the body of the second for is actually an empty statement. You could rewrite the two *for*s like this: <pre><code>int x = 0; for (x = 0; x < 10; x = x + 1) System.out.println(x); int y = 0; for (y = 0; y < 10; y = y + 1) /* Lalala... does nothing at all... */; System.out.println(y); // When control flow gets here, y equals 10 </code></pre> To put more than a statement inside a for, you must use a block, which is a statement composed of many statements. What's misleading for the beginner, is that blocks doesn't have to be associated with for, and actually can exist on their own. The following code in Java is legal: <pre><code> { num = generator.nextInt(sides); System.out.println("You rolled a " + num); } </code></pre> When you put a for which erroneously include the semicolon at the end: <pre><code> for (int num1 = 0; num1 < rolls; num1 = num1 + 1); { num = generator.nextInt(sides); System.out.println("You rolled a " + num); } </code></pre> you are basically saying: <pre><code> for (int num1 = 0; num1 < rolls; num1 = num1 + 1) /* Lalala... does nothing at all... */; { num = generator.nextInt(sides); System.out.println("You rolled a " + num); } </code></pre> Hence your for is executing nothing exactly rolls times, and then it executes the block statement once. Sometimes such errors are mitigated by the fact that the body of a for would reference the iteration variable, num1, but it is not your case. Consider: <pre><code> for (int num1 = 0; num1 < rolls; num1 = num1 + 1); { Console.out.println("Roll No. " + num1); num = generator.nextInt(sides); System.out.println("You rolled a " + num); } </code></pre> This has the ; issue but the compiler detects that there is something wrong because you are using num1 inside the block statement, but due to the ; the block statement was not associated with the for, and hence num1 is out of scope. The following, although having the same logical error, would not result in a compiler error: <pre><code> for (int num1 = 0; num1 < rolls; num1 = num1 + 1); { num = generator.nextInt(sides); System.out.println("You rolled a " + num); } </code></pre> Note: also your while has a similar issue of the extra ; character.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFor statement not working
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdamix911
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFor statement not working
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.