> -----Original Message----- > From: Martin Sebor [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 10, 2006 4:03 AM > To: [email protected] > Subject: Re: [PATCH] Windows infrastructure for generating > VisualStudio projects and solution(s) >
I'll make the all proposed changes. Also I propose to turn on the option /Zc:forScope. This option is present in MSVC 7.0 and later versions (ICC 9.0 and later has this options too) and is off by default. -------------------- /Zc:forScope (Force Conformance in for Loop Scope) Use /Zc:forScope if you want standard C++ behavior for for loops with Microsoft extensions (/Ze). Standard behavior is to let a for loop's initializer go out of scope after the for loop. Under /Ze, the for loop's initializer remains in scope until the local scope ends. -------------------- And another option: /Zc:wchar_t: -------------------- /Zc:wchar_t (wchar_t Is Native Type) If /Zc:wchar_t is not specified, the compiler requires you to either define wchar_t or to include one of the many header files that defines it (for example, wchar.h). Typically, wchar_t is defined as an unsigned short. When the /Zc:wchar_t compiler option is specified, the type wchar_t becomes a native type that maps to __wchar_t in the same way that short maps to __int16. With /Zc:wchar_t, the compiler recognizes wchar_t as a native type. -------------------- When I link the my project (compiled with this option turned on) with stdcxx library I got the linker errors "unresolved external symbol "... <wchar_t> ..."". I propose to add the parameter WCHAR_T:yes/no to the generate.wsf script and Generate the solution projects with option /Zc:wchar_t turned on or off depending on the WCHAR_T parameter. Farid.
