3 ms·

I'm glad to know I'm not the only one abusing compiler macros for "ghetto source control". Having said that, there are plenty of cases where you can't use macr

I'm glad to know I'm not the only one abusing compiler macros for "ghetto source control". Having said that, there are plenty of cases where you can't use macros (like all languages/compilers/interpreters that don't support them). I don't agree with the author here though. Just comment the damn code out normally until you can clean everything up. Doing it that way encourages leaving that mess intact and forgetting about it.

Lagged2Death 13y ago
I don't think that counts as either "ghetto source control" or "abuse" and I'd be interested to find out why you feel this way. I mean, if you're talking about basic C, this (_DEBUG) is actually built-in to most systems from the get-go, for exactly this purpose. "Abuse?"
- niggler 13y ago
  The standard is `NDEBUG`, which (amongst other things) turns off asserts
- dllthomas 13y ago
  I think the parent had in mind introducing and maintaining some feature(s) blocked out in ifdefs for a time, which is sort of ghetto branching.