07-09-2013 08:50 PM
The warning: ... ICL: command line warning #10121: overriding '/Qstdc99' with '/Qstdc++0x' ... is displayed when /Qstdc99 and /Qstdc++0x options are both used, or set to Yes in VS project settings. Even if the warning could be disabled in Disable Specific Diagnostics property of VS project, or with /Qdiag-disable:10121 command line option, a better solution to consider, in case of VS project, is to combine both options in one combobox instead of two comboboxes. I also would like to confirm that /Qstdc++0x always supersedes /Qstdc99 and this is by "design" of these standards. Thanks in advance.
07-12-2013 06:32 AM
C99 only applies to C (it refers to the 1999 C standard) and c++0x (it refers to the 2011 C++ standard) only applies to C++ so it doesn't make any sense to set both on a given source file.
07-12-2013 07:02 AM
>>...C99 only applies to C (it refers to the 1999 C standard) and c++0x (it refers to the 2011 C++ standard) only applies to C++ so >>it doesn't make any sense to set both on a given source file... Do you have Visual Studio 2008 or 2010 with integrated Intel C++ compiler? If Yes take a look at Compiler - Language ( Intel Specific ) section of project properties. There are two comboboxes for these two options. I understand that it is useless to use both options at the same time, for a C-file or for a Cpp-file, but it is allowed to be set (!). I simply wanted to bring attention that these to options need to be combined in one combobox instead of two comboboxes and in that case only one option could be set at any time for some source file.
07-12-2013 06:47 PM
Since there are two ( 2 ) options 4 different states need to be considered: [cpp] 0 ( C99 not used ) -- 0 ( C++0x not used ) 0 ( C99 not used ) -- 1 ( C++0x used ) 1 ( C99 used ) -- 0 ( C++0x not used ) 1 ( C99 used ) -- 1 ( C++0x used ) and here there is a problem since C++0x takes over C99 [/cpp]