what is the order of FOR command

>Wow, I am surprised to read this
Debugging methods are a matter of opinion, it's as simple as that. A good debugger is often a critical tool, but debugging output has it's place as well. It's usually the first method you learn, and you'll use it regularly.

printf() is like triage. Debugging is like a diagnosis.

Quote:

---

Originally Posted by MK27

Wow, I am surprised to read this, but then the only debugger I've tried is gdb.

I was actually thinking of starting a poll (are there polls at cboard?) to find out what people's favourite method of debugging is because mine is definitely

printf

and even

puts("You made it this far...");

which perhaps demonstrates that I could really use a poll of other people's opinions to help me consider more fulfilling alternatives ;)

---

Those are pretty useless output statements.
A debugger will give you that and, oh so much more.
Not to say it does not have its place, as Prelude suggests, however. It does.
But what you use it for is not one of them.

Yuck printf debugging!
Since I learned about the "When hit" option of breakpoints in Visual Studio, I don't recall ever inserting tracing code to debug ever again.