Guh...

Well, so.. I'm on speed. Unintentionally. The good side effect is that I'm coding the hell out of my project.

The bad news... I'm being sloppy. My complex algorithm that I spent weeks on was crashing. Really badly.

So after about 45 minutes of debugging I found the little bastard. I'm going to post it here. If people want an explanation... I can give it. Those of you who actually know code... see if you can see the stupidity I did.

	if (currDepth != newDepth) {
		NSUInteger popCount = currDepth - newDepth;
		NSUInteger popCounter;
		for (popCounter = 1; popCounter <= popCount; popCount++) {
			[[self parserStack] pop];
		}				
	}

Oh, I feel like such a moron.

We now return you to your previously scheduled morning.

Tags: bug, code, sloppy, variables
Current Location: FreePeople House: Sofa wp; Position 1cl2 // v23dh at//kz!
Current Mood: geeky

Wow, what the hell am I doing up at this hour and not at home?

Well, I had one of those rare bugs dumped on my plate that while not really difficuly, is time consuming.

It also would be a really good thing if it were done by a meeting at 11 a.m. tomorrow.

Believe it or not... I don't have to be here. I want to be here. I know with just a few extra hours I can get this thing done and in under the wire... I think.

Well, I understand about 95% of the bug. The question is whether the last 5% will take 10 minutes, 2 hours, or have me scrambling.

So... For the first time at this job; I decided to put in my requisite all night session.

I'm online and doing lots of little fixes for this bug. Meaning... 2-4 lines of code... build for 10 minutes...
leather, wince, re-beat.

Translation: If you're on late night tonight... Feel free to IM. (AIM best, see my profile)...

Otherwise... it's me, the code, and Irene Cara singing about Fame

Tags: all-nighter, bug, late, work
Current Location: Office
Current Mood: tired