DeBug/Release

Who programs mostly in debug, and who programs mostly in Release (ie Not Debug). And why
Mostly = When compileing do you have that buld selected most of the times.

I use debug.
I cannot see why not to, and it catches loads of errors, from typeing to mistakes of logic.
It doesnt seem to take that much longer to compile than release.
(Ok when your building every two minutes it does, but you are only compileing every two minutes because you are looking for errors, so you wouldnt do that in release anyway; well I wouldnt ;(

Nobody in their right mind would program with debug turned off.

You know release is for making smaller, faster exes when you want to release a final version, right?

The names should give a clue what mode to use and when :)

Im not asking when I should use them, Im asking when YOU do. If you dont believe me that some people spend more time compiling to release than to debug, I can look for links for you

I work with it off most of the time. Lots of my stuff tends to be CPU intensive and debug mode is just too slow.

I only use debug when I'm looking for a specific bug.

I believe you - I use the "name method" myself, ie disable debug only when building the finalfinalfinal release version. With todays CPUs it hardly takes (or runs) that much slower either.

At the moment with debug on. However for certain parts of Xmas and Easter Bonus I would program with it on to test new stuff then off for certain tests as the game was too slow with debug on.

I work normally always with debug on. Stuff I know it works correctly gets the nodebug flag especially if it has much loop stuff involved. That way I get the pro of both.
For release I naturally would go the "release" way thought :-)

Same as JP - I work with it off most of the time as it is too slow with it on for some things. Most of the logic in my games is fairly simple though, so I am less likely to make many errors. When I do make mistakes it gets switched on though - usually when I find that a section of code is continually skipped completely for what seems to be an unknown reason.

Having the ability to set break points (I don't just mean the 'stop' command) while in debug mode and stepping through the code would be nice though.

yeah sometimes I get a MAV and then switch on debug mode to find the problem.

This nodebug flag sounds useful, must look into it...

I work with it on. But then when I turn it off I normally forget and work with it off for a while. Then I start to get errors with out any helpful stuff and have to turn it on.

Same as JP. Debug mode is often just too slow when running intensive code.

(On a related note, I wish there was a debug on/off toolbar button in the IDE. I often accidentally run a program in debug mode when I want release mode, and vice versa)

there's a debug mode!!!???!!!???

j/k... i usually work with it off, like a few of the guys above, until something doesn't work as i expected... then i enable it till things are right again...

--Mike

I almost always work with debug mode on. It makes my program alot slower, but that also helps me find slow pieces of code needing optimization. If I can get my program running fast in debug mode, it will run even better in release.

I generally code with debug off then turn it on when I run my program.

@Puki, ;)
So mostly you build debug builds or release builds?

Not sure why- I'm a wierd- because I code in release, and when I get a MAV I turn debug on.

The logic in my code is normally quite intensive which Debug dislikes anyway.

I normally code with debug off and only turn it on when I hit specific errors, although I should probably keep debug on all the time. My stuff is usually pretty simple so there's no noticeable speed difference.

I with John above ... I code in release for everything because stuff just runs too slow and only turn on the debugger when I'm trying to tackle a bug.

I usually code with debug on, but if my program just starts getting too phat, (or if I happen to be using kickass beta modules from someplace that don't like the debugger) I'll be forced to run blindly with scissors.

I use the Max debugger much more often than I ever did the BB/3D/+ debugger though for some reason.

Working with Debug on gives a bit of speed loss which helps to prevent me from making anything too CPU-intensive.