<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Compiler Switch Changes in Visual C++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx</link><description>One noticeable change in the coming release of the Visual C++ compiler is the changes to compiler switches. If you use the project system, when the IDE upgrades your project files, many of these changes will be taken care of automatically. However, if</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Compiler Switch Changes in Visual C++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#439022</link><pubDate>Fri, 15 Jul 2005 02:57:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:439022</guid><dc:creator>mikeb</dc:creator><description>Regarding Zc:wchar_t - I have some code that's breaking becuase of the change in defaults with this switch.&lt;br&gt;&lt;br&gt;Code that pre-VC 2005 relied on wchar_t to be an unsigned short to get overloads to resolve no longer compiles.&lt;br&gt;&lt;br&gt;That's reasonably easy enough to fix (so far)by adding a new explicit override for wchar_t.  However, after doing that the code breaks when compiled with the compiler since there are now 2 overrides for unsigned short.&lt;br&gt;&lt;br&gt;Is there a good way to conditionally compile the wchar_t overloads?  I tried using _WCHAR_T_DEFINED and _NATIVE_WCHAR_T_DEFINED but they're both defined in both compiler cases.&lt;br&gt;&lt;br&gt;I'm currently using #if (_MSC_VER &amp;gt;= 1400) which seems to be working, but it doesn't feel like the best test.&lt;br&gt;</description></item><item><title>re: Compiler Switch Changes in Visual C++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#439231</link><pubDate>Fri, 15 Jul 2005 14:53:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:439231</guid><dc:creator>John Tasler</dc:creator><description>On a current product using VS2003, I've been using the /Fx switch to show me the code injected by attributes. I looked at the VS2005 Beta2 to see if this has been improved, but it has not. I'm sure it's too late in the dev cycle, so please add this suggestion to the next cycle: Let me specify an output directory for the generated files. Perhaps, /Fx:obj\Release, could be the syntax.</description></item><item><title>re: Compiler Switch Changes in Visual C++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#439865</link><pubDate>Mon, 18 Jul 2005 09:03:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:439865</guid><dc:creator>Glenn</dc:creator><description>If nothing else has come out of this article, then it's me learning something about the different compiler switch options. I never knew that the /G switches didn't affect the ability to run the code on older platform, just the optimisations done for them. </description></item><item><title>Brandon Bray e o compilador de C   do VS 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#440153</link><pubDate>Tue, 19 Jul 2005 01:58:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:440153</guid><dc:creator>LA.Net </dc:creator><description /></item><item><title>re: Compiler Switch Changes in Visual C++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#441682</link><pubDate>Fri, 22 Jul 2005 09:19:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:441682</guid><dc:creator>Norman Diamond</dc:creator><description>&amp;gt; Originally, we deprecated the J switch. The&lt;br&gt;&amp;gt; switch changes the meaning of char to mean&lt;br&gt;&amp;gt; unsigned char instead of signed char.&lt;br&gt;&lt;br&gt;I hope you were just writing too tersely, but in case you weren't, and for the benefit of anyone else reading, the meaning of char never means unsigned char or signed char.  Plain char always remains a separate type.  The range of values of plain char matches either the range of values of signed char or the range of values of unsigned char, and it's OK for a switch to alter the meaning of plain char as to which range of values it will get, but the type still has to remain a separate type.&lt;br&gt;&lt;br&gt;At a former employer, I spent a few weeks fixing a program to use unsigned char where it needed unsigned char, and to make its remaining uses of plain char work properly regardless of which range of values plain char would get in any implementation.  A colleague tried to persuade me to use a compiler switch instead.  In a sense my colleague was right:  when the customer says what the customer wants, the customer is right about what the customer wants.  My result worked equally well and was safer for the code but wasn't safe for my career.</description></item><item><title>Tales from a Trading Desk  &amp;raquo; Blog Archive   &amp;raquo; Moving to VC++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#584993</link><pubDate>Thu, 27 Apr 2006 15:19:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:584993</guid><dc:creator>Tales from a Trading Desk  » Blog Archive   » Moving to VC++ 2005</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://mdavey.wordpress.com/2006/04/27/moving-to-vc-2005/"&gt;http://mdavey.wordpress.com/2006/04/27/moving-to-vc-2005/&lt;/a&gt;</description></item><item><title>Compiler Switch Changes in Visual C++ 2005</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#6532903</link><pubDate>Mon, 26 Nov 2007 20:05:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6532903</guid><dc:creator>Compiler Switch Changes in Visual C++ 2005</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://feeds.maxblog.eu/item_272732.html"&gt;http://feeds.maxblog.eu/item_272732.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Website Scripts &amp;raquo; Visual C++ Internals and Practices : Compiler Switch Changes in Visual &amp;#8230;</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#7180725</link><pubDate>Mon, 21 Jan 2008 09:44:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7180725</guid><dc:creator>Website Scripts » Visual C++ Internals and Practices : Compiler Switch Changes in Visual …</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://websitescripts.247blogging.info/visual-c-internals-and-practices-compiler-switch-changes-in-visual/"&gt;http://websitescripts.247blogging.info/visual-c-internals-and-practices-compiler-switch-changes-in-visual/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Warnungen - #define _CRT_SECURE_NO_DEPRECATE | hilpers</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#9337634</link><pubDate>Sun, 18 Jan 2009 13:28:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9337634</guid><dc:creator>Warnungen - #define _CRT_SECURE_NO_DEPRECATE | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.com/958052-warnungen-define-_crt_secure_no_deprecate"&gt;http://www.hilpers.com/958052-warnungen-define-_crt_secure_no_deprecate&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>MFC vs Win32 programming | keyongtech</title><link>http://blogs.msdn.com/branbray/archive/2005/07/08/437078.aspx#9362362</link><pubDate>Thu, 22 Jan 2009 06:57:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9362362</guid><dc:creator>MFC vs Win32 programming | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/2351527-mfc-vs-win32-programming"&gt;http://www.keyongtech.com/2351527-mfc-vs-win32-programming&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>