Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <3AEF8437.DD541895@ece.gatech.edu> Date: Tue, 01 May 2001 23:51:19 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin-apps AT cygwin DOT com Subject: Re: gcc/ansi question References: <20010501231814 DOT A26391 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > It has been pointed out to me that I shouldn't be doing -Dunix when > using the -ansi switch with gcc because the compiler should only define > things which begin with an underscore. I can fix this easily. > > Does anyone know how MSVC handles the WIN32 definitions? Is there an > equivalent switch for Windows which disables the definition of WIN32? > My MSVC installation is currently hosed for some reason so I can't check > this myself. /Usymbol undefines a specific symbol /u (lowercase u) turns off every previously defined symbol "Neither of these options can be used to undefine symbols created with the #define directive. Both options turn off the following Microsoft-specific macros:" _CHAR_UNSIGNED _CPPRTTI _CPPUNWIND _DLL _M_IX86 _MSC_VER _WIN32 _MT Seems kinda wierd to me that -Ufoobar will also cause _WIN32 to become undefined, but that's what the docs say. --Chuck