NSData.bytes is a property of type "void*". And NSPointerFunctions even has a property whose type is a C function pointer: @property (nullable) BOOL (*isEqualFunction)(const void *item1, const

TARGET_OS_MAC is incorrect — for some reason that evaluates to true on all Apple platforms. You want TARGET_OS_OSX instead. Here's the full list as documented in <TargetConditionals.h>, which is the

If you want an actual property encapsulating your C-based array, you could keep it within an NSMutableData object since it’s just bytes. I’m not sure if an NSData object would keep the actual

Dave, close to this topic, I make sure to add a build shell script to export the environment variables to my build process so that on a build, I can get an list of all the build variables for the

You could do that, but I’m doing millions of calculations on the elements of the Array, so it would be a lot slower and much more complex than needed……

Well, you can’t use them as a property anyway, C Arrays *have* to be iVar’s, but I wrap a “Property Wrapper” around the iVars!

Hi all, How do I compile differently depending on the Platform I am compiling for? I have an iOS project, but using the these macros: #if TARGET_OS_IPHONE // iOS code #endif #if

Is there a reason why he shouldn’t represent the values as NIntegers like I suggested before? I didn’t see a response to my suggestion explaining why it’s not a good idea. [myArray

Um, the headline says "How to store C Arrays as a Property ..." so at least one person (the original poster) has said this is about properties. My experience was that properties that are non-pointers

No one said this was a property. It's just an instance variable. Also, it's fine for properties to be C types — after all, there are plenty of integer or boolean properties, and UIKit and AppKit

Can I ask if this discussion is academic or you have already tried? The reason I ask is that property values tend to need to support the NSObject protocol (ie, do the retain/release thing, whether

Whenever you find what you believe to be a bug in Apple's software or web site, write a bug report about it. You might have experienced an edge case no one has yet tested. -- Gary L.

Every where look there are glitches and bugs! What a total nightmare - thanks for letting me know, I thought I was going crazy! Cheers Dave

I’ve heard it *rumoured* (YMMV) that the public release of HS will only support bootable APFS on SSD-only machines - no support for platters or even Fusion platter/ssd drives. That’s a step-back

Yes, Apple won’t let you. Yay, Apple! As long as they are not enabled in the Capabilities part of your project settings, you should be OK. I have felt your pain many many times, good sir. You

Hi, I need to registers 6 Apps on the Apple Developer Site. I’ve done 3 ok, there are LTWiPhoneAppX, LTWiPadAppX and LTWMacAppX these 3 all use GameKit and In-App Purchase and they are enabled

There are much newer versions of this. Check on Apple’s sample files and on Github. Stay away from the old copy that you have.

You can use this: https://github.com/ashleymills/Reachability.swift Nimesh

Hi, A while back I included some code from a sample project that setup Game Center/Kit. This code used a Class called “ Reachability”: Copyright (c) 2011, Tony Million. All rights

The time to read and unwrap an integer from an NSArray is probably under a microsecond, so it's unlikely to be a performance problem. But there's nothing wrong with using a C array. It's what I'd do,