If we go through the trouble of calling juce_LogCurrentAssertion then why on earth aren’t we also printing the message using the preprocessor stringification ?
well, people might not want snippets of their code to be embedded in the binary! I guess it could do that, I’ve always found the filename + line number to be enough info to track it down.
That’s a good point.
For my use cases, and since we’re open source (eventually) we want as much information as possible. Even release builds are built with full symbol information.