Posted by: ojasvirajpal on: November 10, 2009
I discovered this while doing CR for a team mate and now I use it almost always. Though it might not be new for the “pro’s”
but I like it so here it is in the form of a advertisement ![]()
Do u always insert a lot of print statements in your code , which might not be useful output ?
Do u use a lot of print statements while debugging ?
Do u find yourself commenting/deleting those printfs after the code is done and reading them when required again ?
Fear no more enjoy the new -debug option !!!
All u need to do is to check for -debug in the command line options and if its there u print all your print statements (use if(debug){} ) else u don’t
nice ain’t it ![]()
adieu
dude, suggest people to use Visual Studio instead of this ![]()
1. Better option
2. It’s an MS product
@abhishek I agree
@manish Good idea but I am having trouble setting environment variables in Vs any tips ?
@vivek goodidea but u need to recompile, but yes u avoid processing command line arguments.
Wow I mean wow..what a tip.
HCG Levels in Early Pregnancy Thanks for writing this, it was very handy and helped me quite a bit…
Thanks for writing this, it was very handy and helped me quite a bit…
November 10, 2009 at 10:17 pm
dude, making one’s own “-debug” option is extra work…
A truth that will never change: Debugging is always a pain in the ass, be it in a code or in a draft…
Oya Sumi nasai.