Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6014249
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T02:39:53+00:00 2026-05-23T02:39:53+00:00

For debugging I have many calls to a debug log function in my application.

  • 0

For debugging I have many calls to a debug log function in my application. Of course in the production version these debugging calls need to be skipped. Instead of writing:

#if DEVEL == 1
    Log::debug(...);
#endif

around all calls to the debug function I decided the write the following in the debug function itself:

#if DEVEL != 1
    return;
#endif

Will the overhead of the useless function call be avoided by the compiler or am I better off by using (many ugly) #if #endif construction for performance reasons?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T02:39:54+00:00Added an answer on May 23, 2026 at 2:39 am

    Instead of worrying about optimizer, you can do a simple trick:

    #if DEVEL == 1
    #define LOG_DEBUG(...) Log::Debug(__VA_ARGS__)  // variadic macro
    #else
    #define LOG_DEBUG
    #endif
    

    Now use LOG_DEBUG everywhere to keep it simple.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am debugging some code and have encountered the following SQL query (simplified version):
I have several web application projects in one solution. When I start debugging one
I have a problem with an application I'm debugging. Steady state memory usage is
Are there any free Perl IDEs out there for Windows that have debugging capabilities,
Have you managed to get Aptana Studio debugging to work? I tried following this,
I have recently been put in charge of debugging two different programs which will
I have some code in MS VC++ 6.0 that I am debugging. For some
Is it possible to have a post-mortem ( or post-exception ) debugging session in
I am debugging a third-party DLL for which I don't have the source code.
For debugging purposes in a somewhat closed system, I have to output text to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.