• 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: Possible Clang Bug in Initializing Wide String From String Literal?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible Clang Bug in Initializing Wide String From String Literal?


  • Subject: Re: Possible Clang Bug in Initializing Wide String From String Literal?
  • From: Mark Wagner <email@hidden>
  • Date: Thu, 19 May 2011 14:17:28 -0700

On Thu, May 19, 2011 at 08:56, Andreas Grosam <email@hidden> wrote:

> IMHO, if I read the standard correctly, clang seems to make an error here. I hope I'm terrible wrong here, since this is pretty basic stuff. Is there something left to be "implementation defined" what I may have overlooked?
>

Your source code isn't ASCII.  How the compiler handles the non-ASCII
bits (the string literal) is implementation-defined.

--
Mark Wagner
 _______________________________________________
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: Possible Clang Bug in Initializing Wide String From String Literal?
      • From: Chris Hanson <email@hidden>
References: 
 >Possible Clang Bug in Initializing Wide String From String Literal? (From: Andreas Grosam <email@hidden>)

  • Prev by Date: Bug with NSPredicateEditor in Xcode 4
  • Next by Date: Re: Possible Clang Bug in Initializing Wide String From String Literal?
  • Previous by thread: Possible Clang Bug in Initializing Wide String From String Literal?
  • Next by thread: Re: Possible Clang Bug in Initializing Wide String From String Literal?
  • Index(es):
    • Date
    • Thread