JavaScript: Possible uses for #debug directive?

Where I work, all our JavaScript is run through a compiler before it's deployed for production release. One of the things this JavaScript compiler does (beside do things like minify), is look for lines of code that appear like this, and strip them out of the release versions of our JavaScript:

//#debug
alert("this line of code will not make it into the release build")
//#/debug

I haven't look around much but I have yet to see this //#debug directive used in any of our JavaScript.

What is it's possible usefulness? I fail to see why this could ever be a good idea and think #debug directives (whether in a language like C# or JavaScript) are generally a sign of bad programming.

Was that just a waste of time adding the functionality for //#debug or开发者_运维问答 what?

---

If you were using a big JavaScript library like YUI that has a logger in it, it could only log debug messages when in debug mode, for performance.

---

Since it is a proprietary solution, we can only guess the reasons. A lot of browsers provide a console object to log various types of messages such as debug, error, etc.

You could write a custom console object is always disabled in production mode. However, the log statements will still be present, but just in a disabled state.

By having the source go though a compiler such as yours, these statements can be stripped out which will reduce the byte size of the final output.

---

Think of it as being equivalent to something like this:

// in a header somewhere...

// debug is off by default unless turned on at compile time
#ifndef DEBUG
#define DEBUG 0
#endif

// in your code...

var response = getSomeData({foo:1, bar:2});

#if DEBUG
console.log(response);
#endif

doStuffWith(response);

This kind of thing is perfectly acceptable in compiled languages, so why not in (preprocessed) javascript?

---

I think it was useful (perhaps extremely useful) back a few years, and was probably the easiest way for a majority of developers to know what was going on in their JavaScript. That was because IDE's and other tools either weren't mature enough or as widespread in their use.

I work primarily in the Microsoft stack (so I am not as familiar with other environments), but with tools like VS2008/VS2010, Fiddler and IE8's (ugh! - years behind FF) dev tools and FF tools like firebug/hammerhead/yslow/etc., peppering alerts in your JavaScript isn't really necessary anymore for debugging. (There's probably a few instances where it's useful - but not nearly as much now.) Able to step through JavaScript, inspect requests/responses, and modify on the fly really makes debugging alert statements almost obsolete.

So, the //#debug was useful - probably not so much now.

---

I've used following self-made stuf:

// Uncomment to enable debug messages
// var debug = true;

function ShowDebugMessage(message) {
    if (debug) {
        alert(message);
    }
}

So when you've declared variable debug which is set to true - all ShowDebugMessage() calls would call alert() as well. So just use it in a code and forget about in place conditions like ifdef or manual commenting of the debug output lines.

---

For custom projects without any specific overridden console.

I would recommend using: https://github.com/sunnykgupta/jsLogger , it is authored by me.

Features:

• It safely overrides the console.log. Takes care if the console is not available (oh yes, you need to factor that too.)
• Stores all logs (even if they are suppressed) for later retrieval.
• Handles major console functions like log, warn, error, info.
• Is open for modifications and will be updated whenever new suggestions come up.