I try to make a useful macro for logging. But I find that NSLog and all other sort of macros that carry textual information with them simply distract a lot from the code.
Is there any way to “hack” Xcode in a way that it will interpret something like
/*** do this because of that ***/
as a macro call, which results in calling NSLog, for example? I want those logs to “feel” like comments. Anything else that looks like critical code is just distracting and reduces productivity at the end, and then there’s no real benefit from logging what’s going on.
Why do you want to make your code less readable?
The answer is no, and that’s a good thing.
Probably, but that’s useless. All that would do is make the syntax coloring incorrect (coloring this comment as if it were a function call). The compiler (either GCC or Clang) would still see this as the comment that it is.
Making the compiler think it’s a function call or macro invocation is what would actually achieve log output at run time, but even if you could do that, it’s still a bad idea because you would have a function call or macro invocation disguised as a comment.
If you want your program to log messages, write logging code:
This code is explicitly code that does something at runtime. No mystery. No surprises. That’s why it’s better.