• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: SPAM-HIGH: Re: OK on Windows C++
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SPAM-HIGH: Re: OK on Windows C++


  • Subject: Re: SPAM-HIGH: Re: OK on Windows C++
  • From: Clark Cox <email@hidden>
  • Date: Tue, 1 Dec 2009 02:03:10 -0800

On Tue, Dec 1, 2009 at 1:39 AM, Paul Sanders <email@hidden> wrote:
> Actually, it's a #define, and it's part of C99 ('Alternative spellings
> <iso646.h>').  Caught me out too.  It's a just a nuisance, IMO.

No. While that is true for C99, we're talking about C++ here. Please
don't confuse the two. In C, if you don't have the <iso646.h> header
included, then it is perfectly OK to have a variable named "xor",
however the same cannot be said of C++. In C++, it is *never* legal to
have a variable named "xor". Any C++ compiler that allows that is
simply broken.


--
Clark S. Cox III
email@hidden
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: SPAM-HIGH: Re: OK on Windows C++
      • From: Sherm Pendley <email@hidden>
References: 
 >Re: SPAM-HIGH: Re: OK on Windows C++ (From: "Paul Sanders" <email@hidden>)

  • Prev by Date: Re: SPAM-HIGH: Re: OK on Windows C++
  • Next by Date: Framework with static instead of dynamic library?
  • Previous by thread: Re: SPAM-HIGH: Re: OK on Windows C++
  • Next by thread: Re: SPAM-HIGH: Re: OK on Windows C++
  • Index(es):
    • Date
    • Thread