• jeffhung (unregistered) in reply to halcyon1234

    Using some of above #ifdef macros help cooperate with other team members that do not familiar with branching in version control system.

    Yes, that would be some kind of inline-branching version control. XD

  • Cowbert (unregistered)
    ...though it would be interesting to compile a version with all of those macros defined just to see what you'd get.

    Usually -DLINT pulls in everything.

  • LowCoder (unregistered) in reply to jspenguin
    jspenguin:
    What's wrong with just using "#if 0"?

    #define 0 1 Now what will you do?

  • (cs)

    1 #ifdef TOO_MUCH_LOGGING

    Maybe you should try less fibre?

  • Slicerwizard (unregistered) in reply to LowCoder
    LowCoder:
    #define 0 1 Now what will you do?
    Um, watch you try to get that to compile?
  • Stiflers.Mom (unregistered) in reply to halcyon1234
    wtf:
    1 #ifdef BRUT_HAS_A_BUG

    Yes ... a single insect can turn champagne into sewage.

  • T (unregistered)

    Come on.. we're missing the simple solution.

    You need to comment out the #ifdefs with an #ifdef #endif pair eg:

    #ifdef REAL_DELETE delete(stuff); #endif

    becomes

    #ifdef IFDEFS #ifdef REAL_DELETE delete(stuff); #endif #endif

    Now you can compile out all those pesky #ifdefs by defining IFDEFS

  • Travis (unregistered)
    1 #ifdef use_this

    #ifdef or_don't_its_cool_you_know_whatever

    captcha: dolor--madre dia, the pain!

  • Death (unregistered)

    Define all of them... And marvel at the totally different product that emerges that your developers have been working on and selling on the side.

  • Duh (unregistered) in reply to Death
    Death:
    Define all of them... And marvel at the totally different product that emerges that your developers have been working on and selling on the side.

    LOL

Leave a comment on “#ifdef WTF”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article