So?

So, they'll fucking starve. Fatboy will be left with an empty country. Once they're all dead South Korea and China can split it 50/50.

So?

Yea, when passing an array to some random function, debugger generally doesn't show what's inside, so I tend to put prints so I can see what's exactly happening. And I can't wait to get to multithreading. Seems so handy.

I made it once during class, and once home doing preps. Second time found it much quicker.
Sometimes I tend to put semicolon at the end of for loop while debugging some other stuff so it can compile. Once while doing preps I forgot to remove it immediately after debugging. *sigh*
I didn't find it until I started describing to myself what every single line of code does, and that was about hour and a half later. That was the day I started initializing my arrays to 0 so I know when random crap like that happens.

I'm gonna make an amazing programmer one day. *sarcasm in the distance*

It just takes time to learn. I once had to go through a program basically line by line inserting print statements because I had no fucking clue where it'd hang.

Another time while working with multiple threads and semaphores I forgot like 2 lines of code and 3/4s of all threads would hang.

Yea, when passing an array to some random function, debugger generally doesn't show what's inside, so I tend to put prints so I can see what's exactly happening. And I can't wait to get to multithreading. Seems so handy.

When you accidentally put = instead of == when comparing... No warning, no error, no nothing, just a clean compile and weird shit as the output. Dear Lord, that shit took me ages to find.

Yeah what happens is that it causes this:

if(expr1 = expr2){ ... }
expr1 = expr2 // expr1 is set to the value of expr2
so this becomes basically if(expr1){...}, so now the value of expr1 (and 2) is evaluated into a boolean, basically anything non 0 equals true.

So you get something like this
int x = 4, y =5;
while(x = y){ ... }
x becomes 5
5 is not 0 so it evaluates to true, this loop always executes and unless there's a break statement somewhere never stops. It might also stop arbitarily if something in the loop will cause y to become 0.

Personally it's a mistake I only made once.

I made it once during class, and once home doing preps. Second time found it much quicker.
Sometimes I tend to put semicolon at the end of for loop while debugging some other stuff so it can compile. Once while doing preps I forgot to remove it immediately after debugging. *sigh*
I didn't find it until I started describing to myself what every single line of code does, and that was about hour and a half later. That was the day I started initializing my arrays to 0 so I know when random crap like that happens.

I'm gonna make an amazing programmer one day. *sarcasm in the distance*

It just takes time to learn. I once had to go through a program basically line by line inserting print statements because I had no fucking clue where it'd hang.

Another time while working with multiple threads and semaphores I forgot like 2 lines of code and 3/4s of all threads would hang.

Yea, when passing an array to some random function, debugger generally doesn't show what's inside, so I tend to put prints so I can see what's exactly happening. And I can't wait to get to multithreading. Seems so handy.