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 577081
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T14:06:55+00:00 2026-05-13T14:06:55+00:00

I am using a API that has a macro for success which is NT_SUCCESS.

  • 0

I am using a API that has a macro for success which is “NT_SUCCESS”. However they don’t have one for failure. So normally I have to do this.

if(something failed)
    return !NT_SUCCESS;
else
   return NT_SUCCESS;

Having the !NT_SUCCESS I don’t think is very readable. So I decided to do this:

#define SUCCESS NT_SUCCESS
#define FAILURE (!NT_SUCCESS)

EDIT =============================

#define ENT_NOERR 0 /* No error */ 
#define NT_SUCCESS ENT_NOERR /* synonym of ENT_NOERR */ 

This is how NT_SUCCESS is declared, Would it still be ok to do what I have done.

Would that be ok?

Many thanks for any suggestions,

  • 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-13T14:06:55+00:00Added an answer on May 13, 2026 at 2:06 pm

    I would add parentheses for good measure, but otherwise you should be OK:

    #define FAILURE (!(NT_SUCCESS))
    

    This is “just in case”, to prevent bad definitions such as #define NT_SUCCESS 1+1. Of course, no sane implementation would do this, so your definition should be okay too. But it can’t hurt to be paranoid. 🙂

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

Sidebar

Related Questions

I'm using a Python API that expects me to pass it a function. However,
I have a need to create a transactional process using an external API that
I have a program that creates a Windows user account using the NetUserAdd() API
I am using an api which interacts with a db. This api has methods
I'm using an API that requires me to pass a function pointer as a
Using the Win32 API (in C, but that's inconsequential), how can I tell if
I have created a minidump using win32 api [DllImport(DbgHelp.dll, SetLastError = true)] private static
I'm using and testing a VbScript API using JavaScript. One part of the VbScript
I am using Scribd API (www.scribd.com) to display the PDF files in my website.
Am building a Book search API using Lucene. I need to index Book Name,Author,

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.