• 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: Character encoding of C-string runtime functions?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Character encoding of C-string runtime functions?


  • Subject: Re: Character encoding of C-string runtime functions?
  • From: Rick Mann <email@hidden>
  • Date: Tue, 11 Jun 2013 14:36:39 -0700

On Jun 11, 2013, at 14:32 , Greg Parker <email@hidden> wrote:

> Formally unspecified. It's possible to create a selector or class at runtime with arbitrary zero-terminated bytes and the runtime won't care.
>
> In practice you should use UTF-8. That's what the compiler does.

Thanks. That's what I've always done, but I wondered, since by default Xcode used to make files UTF-16. At least, it did the strings file. Now it seems my files are all UTF-8, so I would imagine that would (should) drive the encoding.

--
Rick




_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Character encoding of C-string runtime functions? (From: Rick Mann <email@hidden>)
 >Re: Character encoding of C-string runtime functions? (From: Greg Parker <email@hidden>)

  • Prev by Date: Re: Character encoding of C-string runtime functions?
  • Next by Date: Re: Staying on integrated GPU while using NSOpenGLView
  • Previous by thread: Re: Character encoding of C-string runtime functions?
  • Next by thread: NSNotFound signed???
  • Index(es):
    • Date
    • Thread