943,621 Members | Top Members by Rank

Ad:
  • C++ Discussion Thread
  • Unsolved
  • Views: 2266
  • C++ RSS
Oct 7th, 2008
0

Preprocessor #warning Command Question

Expand Post »
Is there a way to #define something as a #warning?
I tried using the following code, but it gives me an error:
'warning' undeclared (first use this function)

This is the part of code where the error appears:
c++ Syntax (Toggle Plain Text)
  1. #define something #warning This is not a standard function!
  2.  
  3. int main(void)
  4. {
  5. something
  6. return 0;
  7. }


Any help on this please?
If it's not possible to perform, please tell

Thanks in advance
Last edited by unbeatable0; Oct 7th, 2008 at 10:45 am.
Reputation Points: 42
Solved Threads: 13
Junior Poster in Training
unbeatable0 is offline Offline
90 posts
since Sep 2008
Oct 7th, 2008
0

Re: Preprocessor #warning Command Question

Never mind, I found the answer
Reputation Points: 42
Solved Threads: 13
Junior Poster in Training
unbeatable0 is offline Offline
90 posts
since Sep 2008
Oct 7th, 2008
0

Re: Preprocessor #warning Command Question

Oh well... I was wrong. My method didn't work
Please help me
Reputation Points: 42
Solved Threads: 13
Junior Poster in Training
unbeatable0 is offline Offline
90 posts
since Sep 2008
Oct 7th, 2008
0

Re: Preprocessor #warning Command Question

I don't think the pre-processor is capable of expanding lines which are themselves pre-processing statements.

In short, I don't think it's going to work.
Team Colleague
Reputation Points: 5862
Solved Threads: 950
Posting Sage
Salem is offline Offline
7,164 posts
since Dec 2005
Oct 8th, 2008
0

Re: Preprocessor #warning Command Question

Any help on this? If it helps, I want the macro to be a function. For example:

c++ Syntax (Toggle Plain Text)
  1. #ifndef _WINDOWS_H
  2. #define test(); #warning <windows.h> needs to be included for this function!
  3. #endif
  4. int main(void)
  5. {
  6. test();
  7. return 0;
  8. }

If it's not possible to do this way, is there another way to do it, which will give a warning instead of the function, in case the function cannot be used?
Last edited by unbeatable0; Oct 8th, 2008 at 4:46 am.
Reputation Points: 42
Solved Threads: 13
Junior Poster in Training
unbeatable0 is offline Offline
90 posts
since Sep 2008
Oct 8th, 2008
0

Re: Preprocessor #warning Command Question

Salem is right; there is no way to #define a macro that expands to a preprocessor directive.

There is also the incidental concern that #warning is not a standard preprocessor directive.

Any C++ compiler will generate an error on an attempt to call a function that has not previously been declared.

I can't see the point of what you're trying to do. If <window.h> is not included
C++ Syntax (Toggle Plain Text)
  1. #ifndef _WINDOWS_H
  2. #error <windows.h> needs to be included to compile this source file
  3. #endif
will generate an error message that gives specific information on requirements.

Of course, if you need to use the above (eg if you have a header that relies on <windows.h>) it would be easier to #include <windows.h> anyway
Reputation Points: 193
Solved Threads: 32
Posting Whiz in Training
grumpier is offline Offline
206 posts
since Aug 2008
Oct 8th, 2008
0

Re: Preprocessor #warning Command Question

> #define test(); #warning <windows.h> needs to be included for this function!
But if you don't have windows.h, then the code would have failed to compile before this point anyway.

How to tell your OS/Compiler/etc at compile-time
http://predef.sourceforge.net/

You have to do something like this
C++ Syntax (Toggle Plain Text)
  1. #ifdef _WIN32
  2. #include <windows.h>
  3. #else
  4. #warning needs windows.h
  5. // in case the compiler ignores #warning
  6. int test ( ) {
  7. fprintf( stderr, "_WIN32 not set, compilation should have failed!\n" );
  8. exit( 0 );
  9. return 0;
  10. }
  11. #endif

Or if you're trying to spot obsolete functionality, and you're using gcc, then perhaps this (this is the 2nd obscure snippet from the gcc manual today )
Quote originally posted by gcc manual ...
deprecated
The deprecated attribute results in a warning if the variable is used anywhere
in the source file. This is useful when identifying variables that are expected
to be removed in a future version of a program. The warning also includes the
location of the declaration of the deprecated variable, to enable users to easily
find further information about why the variable is deprecated, or what they
should do instead. Note that the warning only occurs for uses:
extern int old_var __attribute__ ((deprecated));
extern int old_var;
int new_fn () { return old_var; }
results in a warning on line 3 but not line 2.
Team Colleague
Reputation Points: 5862
Solved Threads: 950
Posting Sage
Salem is offline Offline
7,164 posts
since Dec 2005

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Message:
Previous Thread in C++ Forum Timeline: factoring binomials
Next Thread in C++ Forum Timeline: Need help with AddFontResource





About Us | Contact Us | Advertise | Acceptable Use Policy
Forum Index | Build Custom RSS Feed


Follow us on Twitter


© 2011 DaniWeb® LLC