Not in this case. First, i is declared and assigned a value of 0. Next, x is declared and assigned a value of -i or -0. On the first loop iteration, i will decrement to -1, perform the conditional check, then execute the loop body which will assign x to -i or -(-1) or positive 1, and so on.
The only time a variable is created without a value is if you declare one without assigning a value like with
I know. OP asked what x was before the loop, and I just said it’s an int. The int can be any value because as you pointed out it will be set to 0 in the first loop iteration.
Shit, you’re right. x is declared inside the loop, so it doesn’t exist until the loop begins execution.
Technically, I suppose you could say the compiler will allocate memory for x without assigning a value before the loop is executed and… I’m understanding what you mean now, I think.
The code seems to be C-style language with curly braces and types in front for variable declarations, probably java. This means the variable must be declared of screen before the loop or it would not compile. It could have a previous value or be uninitialized, but that does not affect the end result.
An int. Value doesn’t matter because it’s overwritten.
Not in this case. First, i is declared and assigned a value of 0. Next, x is declared and assigned a value of -i or -0. On the first loop iteration, i will decrement to -1, perform the conditional check, then execute the loop body which will assign x to -i or -(-1) or positive 1, and so on.
The only time a variable is created without a value is if you declare one without assigning a value like with
[int]i;
I know. OP asked what x was before the loop, and I just said it’s an int. The int can be any value because as you pointed out it will be set to 0 in the first loop iteration.
Shit, you’re right. x is declared inside the loop, so it doesn’t exist until the loop begins execution.
Technically, I suppose you could say the compiler will allocate memory for x without assigning a value before the loop is executed and… I’m understanding what you mean now, I think.
The code seems to be C-style language with curly braces and types in front for variable declarations, probably java. This means the variable must be declared of screen before the loop or it would not compile. It could have a previous value or be uninitialized, but that does not affect the end result.