Hi,
why do i get error: 'strcmp': identifier not found in visual studio 2010 C++ Express
#include <string.h>
#include "stdafx.h"
int _tmain(int argc, _TCHAR* argv[])
{
printf("%d",(int)strcmp( "str1", "str2" ));
return 0;
}
Thanks
views:
164answers:
1
+15
A:
:( #include <string.h> :(
#include "stdafx.h"
Fun quirk of the MSVC compiler, it generates the exact same error when you compile it like that. Yes, not a lot of 'fun'. It skips everything to find the stdafx.h precompiled header include directive. The string.h doesn't actually get included. Fix:
#include "stdafx.h"
#include <string.h>
Always put the stdafx.h include first.
Hans Passant
2010-09-13 21:48:27
That is quite possibly the most ridiculous behavior I've ever heard of from a compiler. WTF
Tyler McHenry
2010-09-13 21:49:35
Good catch. The compiler should warn you about this.
Mark Ransom
2010-09-13 21:50:45
Alternatively, you can disable pre-compiled headers setting
AndreyT
2010-09-13 21:54:37
@Tyler: no argument from me. Pointing out what C or C++ Standard dictum they violated is however tricky. It is the 'hello world' smoke-out test to a tee, a mistake you only ever make once.
Hans Passant
2010-09-13 21:56:43
"Pointing out what C or C++ Standard dictum they violated is however tricky." Perhaps I'm missing something, but how can they not violate the standard? E.g. "6.10.2 Source file inclusion" of C99 standard.
Roman Cheplyaka
2010-09-13 22:04:16
I don't know what I did to my VS (*at work; can't check now*), but I can compile C sources without that `stdafx` stuff (possibly, from the comments, I turned off pre-compiled headers) and with a proper `main`.
pmg
2010-09-13 22:26:14
@Roman Cheplyaka: MSVC doesn't even *try* to be C99 conformant. Source file inclusion is the least of its problems.
Stephen Canon
2010-09-13 22:33:38
@pmg: yes, you can do the sword-fighting thingy if you choose. If you never tried it before, pre-compiled headers done the right way is only a few seconds of your life instead of many minutes.
Hans Passant
2010-09-13 22:35:49
@Roman: Precompiled headers are an implementation-specific compiler optimization for improving compile times. In order to improve compile time, an additional requirement is imposed on your source: you must include the designated header first. You can disable this feature, so I can't see how it's a violation of any language standard: it's just an implementation-specific language addition.
James McNellis
2010-09-13 23:51:42
Visual C++ should also emit a level 1 warning: "warning C4627: '#include <string.h>': skipped when looking for precompiled header use." If you ignore that warning, then yes, this might be considered "WTF" compiler behavior.
James McNellis
2010-09-13 23:55:20