does your version differ?
> On Aug 12, 2015, at 8:07 PM, André Francisco
> wrote:
>
> Hi all,
> I've been reading about object initialisation in Objective-c, as well as the
> recent additions of NS_UNAVAILABLE and NS_DESIGNATED_INITIALIZER. It's been
> confusin
-0700
CC: cocoa-dev@lists.apple.com
To: andre.frate...@hotmail.com
On Aug 12, 2015, at 8:07 PM, André Francisco
wrote:I've been reading about object initialisation in Objective-c, as well as
the recent additions of NS_UNAVAILABLE and NS_DESIGNATED_INITIALIZER. It's been
confusing
Hi all,
I've been reading about object initialisation in Objective-c, as well as the
recent additions of NS_UNAVAILABLE and NS_DESIGNATED_INITIALIZER. It's been
confusing what the correct approach would be, mostly due to limitations imposed
by the compiler. My main goal is obviously to ensure pr
threat is just crashing the app.
Cheers.
> Subject: Re: NSSecureCoding with containers (or, is NSArray lying?)
> From: graham@bigpond.com
> Date: Fri, 17 Jul 2015 09:52:33 +1000
> CC: r...@rols.org; cocoa-dev@lists.apple.com
> To: andre.frate...@hotmail.com
>
>
&g
own logic all the way down you can make it as secure as you
like, just don’t use the collection classes automatic encode/decode support.
On 16 Jul 2015, at 10:17, André Francisco
wrote:(I'm new to the mailing list and I'm not sure whether I should reply just
to Roland or everyone. P
> From: r...@rols.org
> Date: Thu, 16 Jul 2015 09:49:24 +0800
> CC: cocoa-dev@lists.apple.com
> To: andre.frate...@hotmail.com
>
>
> > On 16 Jul 2015, at 08:30, André Francisco
> > wrote:
> >
> > Hi all,
> > I posted a question at SO
> >
Hi all,
I posted a question at SO
(http://stackoverflow.com/questions/31307331/how-to-use-nssecurecoding-with-id-objects)
and despite the bounty it still didn't get any answers. I am not confident
that it will either.
The problem is when implementing NSSecureCoding with a collection (or
contain