Yeah, sorry, I just meant anything that’s outside the actual juce codebase itself.
An example of compromise is the huge tracktion engine module, where it’d take days to replace all the uses, so we added juce:: to all the uses in the header files, but each cpp file has its own using namespace juce; inside it, after all the includes. That’s pretty safe, but still something we should go back and tidy up one day when bored.
I’d like to add in light of the recent discussions on use of auto, using auto means you have to spell out juce:: far less than you would have before we had the feature.
