Programming Frustrations

I think programmers are required to get angry when they can''t track down frustrating bugs.

Right... and programmers'' block happens to me every few weeks or sometimes days.

- JQ, PWC Software
"There are no pessimists, optimists and realists; just pessimists and optimists who think they're realists" -me

I''ve gotten angry at features that don''t work. In fact, I''m angry right now, because I''m trying to copy a bitmap to an off-screen surface in DirectDraw, and when it hits certain lines(I''m still trying to track down the culprits), my program terminates for no reason!

:( :( :( :( :( :( :( :( :( :( :( :(
I just know I'm gonna catch hell for this...
:( :( :( :( :( :( :( :( :( :( :( :(

I hate it when I can get something to work in one program, but can''t move it to another without major problems.
Here''s one thing that really pissed me of once:

#include <stdio.h> #include <stdlib.h> void main(void) { FILE *in; if((in=fopen("new.txt","r"))==NULL) { perror("Error:"); exit(1); } . . . }

and then I take the exit(1) out and I get an error when trying to load new.txt and my computer shuts down all on it''s own. Just BAMM!!! and it''s out like a light. I was so frickin'' scared, especially since it''s my parents computer and they have their finances on it. Luckily they weren''t home right then, so they never knew it happened.

shut up
CAN I GET A WOO WOO!

The thing I hate the mst is taht I can trak down bugs in other people''s program faster than most of my lecturers ... but as soon as I sit down at my keyboard, I suddenly turn dumb and forget simple things . But I have learnt to take care of that, I jsut take a big massive break, and when I ome back, the fault is blindingly obvious ... and I hit myself, gasping in a loud "D''OH!"

youpla :-P

ArchWizard-
I know EXACTLY where you''re coming from... putting a bitmap in an offscreen, then actually trying to display it always gives me trouble to! GRRRR

Hehe, I can also relate to the post above. A few days ago I was stuck so badly on a piece of code, but as it turned, it was a simple thing like unlocking the primary surface before leaving the main loop. Duh.

It is these kinds of errors that make me become stuck for a long time, but when it comes to the complex ones- it''s a matter of minutes before I''ve defeated it. Funny how it works!

If you place an infinite amount of monkeys in a room with an infinite amount of type-writers, they WILL type up the entire workings of Shakespeare before the next minute is over.

I noticed and fixed a very frustating bug in my code yesterday, though now that I solved it, it seems so simple I wonder why I didn''t notice it earlier.

I have a "module"-based engine, where there''s one main class that handles the modules, error logging and messages etc. It stores the list of modules in an STL linked list. When the main class is closed, it also closes all of the modules, then exits the application. The problem was that the module classe''s Close function also removes the item from the linked list. So, when I iterated through the modules and closed one, it invalidated the iterator, and the program crashed. Ugh.

-Jussi

"As I draw up my breath,
And silver fills my eyes.
I kiss her still,
For she will never rise."
- My Dying Bride

LOL capn_midnight, that kinda thing has happned to me too!! I was like.. oh S$@# what have i done... But things always seem to boot up fine after the fact, hehe, thank goodness.

I''m going through hell to become good in programming. It can be wonderful when you can solve current problems with previous knowledge you acquired. Right now I''m stuck on functors in STL particulary the mem_fun1() in for_each(input it_f, input it_l, mem_fun1(objA::show)) thing. Somehow that syntax isn''t working maybe tomorrow it will