为您找到"
#define INVALID
"相关结果约100,000,000个
So maybe there's one in the definition of INVALID_VALUE? Look up at #define INVALID_VALUE -999; and there it is! Think it should be there, but not sure? So let's try remove it and see if it works. Success! This page goes and explains why you shouldn't conclude a #define with a semicolon, even if it is needed in the use of the macro.
When i'm trying to compile a program with #DEFINE it says: 2:2: error: invalid preprocessing directive #DEFINE Why, and how do i fix it?
Spaces or tabs are permitted between the # and define, but not escape characters or other symbols or macros. The preprocessor removes whitespace and concatenates the # and define together. The following are valid uses: #define my_macro # define my_macro # define my_macro The following are invalid uses: #define empty_macro
#define is commonly used to define constants that are replaced by their values during preprocessing. Used to define simple macros that removes the repetitive code from the program. Used for conditional compilation to include or exclude certain sections of code based on specific conditions. Used to shorten lengthy expression present in the program.
The #define creates a macro, which is the association of an identifier or parameterized identifier with a token string. After the macro is defined, the compiler can substitute the token string for each occurrence of the identifier in the source file.
In C programming, #define is a preprocessor directive that is used to define macros. The macros are the identifiers defined by #define which are replaced by their value before compilation. We can define constants and functions like macros using #define.
Of course, it is also possible to write invalid#define directives that have one or more of these little items or to write valid #define directives and then use them improperly, but they are not prohibited by the language. Bottom line: To the Original Poster: How the heck can anyone guess what the problem really is unless we see some code?
#define is a preprocessor instruction that defines a macro. In your case macro dItemName with value L"CellPhone". Macros are bad mostly because they are processed before the actual code is. This means that they aren't subjected to scopes and to the rules of C++ syntax.
Is this in a C file or C++? Your #define is in C. Make sure you're on the same build configuration as you have the #define set up in. Release or Debug. Do a sanity check and put some invalid syntax in the part you think it should be running to see if the compiler is compiling what you think it is.
The GLSL specification (this text appears to be the same in all versions of the specification) says this: #define and #undef functionality are defined as is standard for C++ preprocessors for macro...