Just a real quick question here... When you write a game, or any program, do you write ALL the code, then debug?? Or do you code parts of it, make sure they work, then put them all together? Is it potentially impossible to debug a completly coded program? Thanx for all you continuing help! The Shaz "You''ve got two empty halves of coconuts and your bangin'' ''em together!!" -Monty Python and the Holy Grail

It''s not impossible to debug a completely coded program, but it''s DAMN hard. You should always debug new functions/classes as soon as you are done writing them. It''ll save lots of time in the long run.


- Houdini

Thanx a bunch!!

The Shaz

"You''ve got two empty halves of coconuts and your bangin'' ''em together!!" -Monty Python and the Holy Grail

As stated, you should debug each routine/class seperately. Run it through all of its courses. Make sure it knows how to handle every situation it should be able to handle. That way, down the line when something goes wrong, you can be reasonably sure that it''s in the new code, not the stuff you wrote last week. It saves on a hundred headaches, and I''ve noticed in my code that it prevents the major bugs from ever appearing.

Micah