And that's why I am not a professional programmer. I would just be stuck looking at it like a monkey looking at type writer. Eventually I would just throw poop at it and walk away.
Really? Seems like a straightforward issue from the very first part of the link.
int index() {
int index = this.index.get();
if (index < 0) {
index -= Integer.MAX_VALUE;
}
return index;
}
The part that mutates the index count is an obvious potential problem source when the index goes all to hell. A conditional on index < 0 tells you that you're trying to deal with signed versus unsigned data type. It should be fairly obvious what's going on, provided you've spent a bit of time messing around with binary representations of numbers.
7 comments
3 u/wafflesid 29 Aug 2015 01:34
And that's why I am not a professional programmer. I would just be stuck looking at it like a monkey looking at type writer. Eventually I would just throw poop at it and walk away.
9 u/BlueSpeed 29 Aug 2015 02:54
At least they didn't have to deal with a hardware bug like the developers of crash bandicoot.
1 u/wafflesid 29 Aug 2015 04:17
Oh maaaaan. That would suck.
1 u/Balrogic 30 Aug 2015 04:47
Really? Seems like a straightforward issue from the very first part of the link.
The part that mutates the index count is an obvious potential problem source when the index goes all to hell. A conditional on index < 0 tells you that you're trying to deal with signed versus unsigned data type. It should be fairly obvious what's going on, provided you've spent a bit of time messing around with binary representations of numbers.
Edit: Removed a brain fart, still waking up.
1 u/wafflesid 30 Aug 2015 07:11
Here, have a cookie.
0 u/JesusChrist2 30 Aug 2015 06:29
fuck spotify
0 u/President-Sanders 02 Sep 2015 10:05
This is the dumbest fucking "look how clever I am" shit, that's why it's shit.