• 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: Xcode incorrect 'uninitialized' warning?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode incorrect 'uninitialized' warning?


  • Subject: Re: Xcode incorrect 'uninitialized' warning?
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 07 Feb 2017 16:49:39 -0800


On Feb 7, 2017, at 3:41 PM, Quincey Morris <email@hidden> wrote:

Also, you can probably use a C struct initializer to make this go away, and be more efficient too. I dunno the exact syntax details, but something like:

 CPTImageSlices imageSlices = { 9 *  NULL };

All you need is
 CPTImageSlices imageSlices = {  };
since omitted struct fields default to zero.

And if you need to zero out an array after its declaration, it’s most efficient to call memset() rather than iterate over the elements.

—Jens
 _______________________________________________
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

References: 
 >Xcode incorrect 'uninitialized' warning? (From: Carl Hoefs <email@hidden>)
 >Re: Xcode incorrect 'uninitialized' warning? (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: Xcode incorrect 'uninitialized' warning?
  • Next by Date: Re: XCode codesigns my App but Gatekeeper says "unidentified developer" nonetheless
  • Previous by thread: Re: Xcode incorrect 'uninitialized' warning?
  • Next by thread: Suddenly have to register my watch???
  • Index(es):
    • Date
    • Thread