ivan.cuevas Posted September 4, 2015 Share Posted September 4, 2015 Hi all, I think I have found a bug related to preprocessor's behavior with #if expressions. In the attached sample, when a variable is defined in a conditional expression, the later expressions ignore it despite of the variable is properly defined. if_preprocessor.zip Link to comment
silent Posted September 4, 2015 Share Posted September 4, 2015 Hi Iván, Yes, you are absolutely right :) Temporary workaround for this issue is to replace code starting from line 12 to this: #ifdef USE_TEST_VARIABLE_1 #define TEST_VARIABLE 1 #endif // USE_TEST_VARIABLE_1 #ifdef USE_TEST_VARIABLE_2 #define TEST_VARIABLE 2 #endif // USE_TEST_VARIABLE_2 #ifdef USE_TEST_VARIABLE_3 #define TEST_VARIABLE 3 #endif // USE_TEST_VARIABLE_3 This issue will be fixed in the next SDK update. Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
silent Posted September 9, 2015 Share Posted September 9, 2015 All the UnigineScript offtopic messages were moved: https://developer.unigine.com/forum/topic/3483-uniginescript-and-c/ How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Recommended Posts