Build option to remove console.* statements

[Michael Schall]

I just found the wonder of the dojo.profile namespace. I would like to add profile statements to all my widgets/modules. It would be great if the build system would remove them from the dojo.js file. Personally I would like to leave them in the rest of the release folder. Is the rest even even "built"?

[dylan]

Perhaps we can do this as part #1357 ?

[dylan]

unfortunately not going to make it into 0.4, pushing to 0.5

[Adam Peller]

We don't have dojo.profile anymore, but there are profiling options on console, and we could possibly remove all console.* references in a build. Should we do this? This doesn't sound like a 0.9 thing.

[dante]

i'm +1 automatically stripping console.log/dir from the code in release builds (or any build for that matter?) ... they are helpful to in test cases, but have limited use within the codebase on a permanent basis.

[Adam Peller]

I'm -1 on removing some of the console.* statements, like console.error/warning. log and debug seem okay, but we need a 'style' statement about this before we change the build.

[dylan]

ok, will push out until we decide on a preferred approach.

[James Burke]

For this to work well, I'll need the parens-matching code needed for #2536.

[James Burke]

Stealing from alex so it shows up in my bug search. Feel free to take it back if you really want it.

[James Burke]

Fixed in r14254.

[James Burke]

(In [14256]) Refs #1368: make sure console calls are still useful outside of built files that have the calls stripped.

[James Burke]

(In [14258]) Refs #1368: make sure xdomain warnings are really warnings.

[James Burke]

(In [14260]) Refs #1368: make sure xdomain warnings are really warnings. \!strict