just a little idea here. i mean since DBG() is a very cpu intensive method anyway why not make it even worse and add the possibility to give it a bunch of numbers without wrapping String() around them all the time? that could be pretty handy imo. image a method that takes an unspecific amount of numbers and automatically formats them like this in the output:
34545 :: 345.3434 :: 2323 :: 420.69
just by writing DBG( 34545, 345.3434, 2323, 420.69);
The problem with DBG is not the CPU, it is it needs asynchronous access to the console to print, so it is waiting for a lock on OS level. There is nothing that you can (or should bother) optimise.
oh it does… is that new? when i started with juce (some weeks or months ago) i still had to use String() around all numbers in DBG. i already thought i had to figure out how to pass a variable number of arguments to a function to write my own printing method