Happiest moment: It runs for more than 3 1/2 microseconds without trying to overwrite some vital part of my hardrive or develop 16,000 memory leaks each the size of a small dog and able to (i swear) physically eat holes in my disk.
Nah! It's finding/fixing those bugs that makes it interesting for me! And isn't it always something stupid, in a routine that could not possibly be the cause, that you've looked at 50 times but decided that one is fine, that doesn't interface with the bit that seems to be the cause...
Thank you adrian! You've made my day a little better. :) I was begining to worry that this happened only to me. You summed it up exactly.
I spent a good portion of yesterday beating my brains out trying to figure out why something was behaving incorrectly. From the looks of things it seemed the only possible problem was that that x must != y even though when i output x to file and check it, x does = y... After hours of debugging this i accidentally scrolled too far down the page and the code jumped out and struck me... It appears that i had a clause that skipped the function i was working on and used an alternate function if x was a certain number... I'd written the code so long ago i had forgotten about it. Thats about when your draw drops to your knees and you cant believe you've wasted all this time hunting ghosts.
After fixing that little sucker i of course felt better but there was still that little part in the back of my mind still kicking myself for missing the obvious for sooo long. The complex stuff never eludes me... Go figure. :)