Re: compiling iso c++ code in Visual Studio environment
"RS" <rsina_no.ssppaamm@comcast.net> wrote in message
news:cs6dnRz3c8qc023ZnZ2dnUVZ_qidnZ2d@comcast.com...
My code compiles well with gcc on linux and OS X, but now I have to run it
at work, and my only choice is Visual Studio .Net 2003 environment on
windows, which I had never used before. I've noticed several obstacles
with the compilation. For example this environment insists that we put all
headers under a stdafx header, which I managed to find a way to get
around.
The compiler doesn't do that. Because most of the solutions built with the
tool have to include a bazillion-line Windows header, the IDE chooses to
stuff the common includes for a project into stdafx.cpp, compile that and
include the already compiled result into every other module that in other
environments would include them separately. It speeds compilation, that's
good. But it can get in the way.
But there are other issues. For example, Visual Studio claims that there
is no such thing as std::numeric_limits. Also, it gives a bizarre error
that there is something wrong with the stdio headers in my files-- except
that I don't use stdio, I use iostream.
There are a number of regulars here who have seen and done it all. If you
post a short snippet that you are having trouble with along with the exact
text and number of the diagnostic you are almost guaranteed a reply.
For example, is there an option to check to let it know we are compiling
iso code?
See here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_.2f.za.2c_2f.ze.asp
Also, are there any online tutorials or guides for people who need to
migrate from gcc to visual Studio 2003?
I expect someone will suggest something if there are any. Google came up
empty for me.
Regards,
Will