Quote:
Quote:
The error comes in on Level 22 because a single byte cannot be greater then 255. The result then "flips" over to 4 (260-256). And there's your bug! Obviously the programmers never considered that people would make it that far.
isn't this basically a memory limitation?
Horribly nerdy response:
Though it might depend on the definition of the term, this (I would imagine) would not be called a memory limitation, and certainly wouldnt be called "running out of memory"
Generally, to say that something ran out of memory means that the program tried to set aside space for a variable and there wasnt any room left.
That didnt happen here (the variable was already created) And, its unlikely that if the programmers forsaw this problem, they would not have been able to allocate a second byte to make the variable's range 256 times bigger. So, basically, it was a programming error not a memory limitation.
EDIT: even more completely useless posting: if you wanted to say that the fact they didnt have a logic check for the overflow was a memory limitation (since these additional instructions would have taken up more, and perhaps too much, memory) I would agree