Well, the Debuglog becomes inactive so it's reasonable to assume there is no code generated.
Can we be sure? I suppose not. So let's try a quick test.
Create an exe with Debug mode turned off. Check the file size.
Now comment out one of the DebugLog lines and try again. File size is exactly the same.
This shows that there was no DebugLog code.
The remaining reference to DebugLog guards against the possibility the compiler doesn't generate code if DebugLog is never used.
I don't think Blitz does this sort of optimization, but it can't hurt to be paranoid.
Can we be sure? I suppose not. So let's try a quick test.
Open in online IDEDebugLog "one" DebugLog "two" Stop
Create an exe with Debug mode turned off. Check the file size.
Now comment out one of the DebugLog lines and try again. File size is exactly the same.
This shows that there was no DebugLog code.
The remaining reference to DebugLog guards against the possibility the compiler doesn't generate code if DebugLog is never used.
I don't think Blitz does this sort of optimization, but it can't hurt to be paranoid.