> On 6 Jul 2016, at 7:10 AM, Jonathan Taylor
> wrote:
>
> Quicktime. My code has been 32-bit only since I first wrote it, because I
> make use of the APIs in QuickTime/ImageCompression.h for encoding movies.
Not really quite on-topic, but if you are having to switch to a whole new API,
a po
On 5 Jul 2016, at 22:22, "Gary L. Wade" wrote:
> You might need to write some lower level stuff, but some of the things in
> there can be done, albeit differently. Apple knows I've submitted a number of
> bugs and incident reports to get codecs supported in later frameworks. Do the
> same. It m
>> Quicktime.
>
> Oh, you poor thing. That’s one nasty API. (Actually dozens of nasty APIs.) O_o
Yep. I rely on code that I worked out years ago, with the help of examples on
the internet, and I do my best to leave that code untouched!
>> My code has been 32-bit only since I first wrote it, bec
You might need to write some lower level stuff, but some of the things in there
can be done, albeit differently. Apple knows I've submitted a number of bugs
and incident reports to get codecs supported in later frameworks. Do the same.
It may happen.
--
Gary L. Wade (Sent from my iPhone)
http://
> On Jul 5, 2016, at 2:10 PM, Jonathan Taylor
> wrote:
>
> Quicktime.
Oh, you poor thing. That’s one nasty API. (Actually dozens of nasty APIs.) O_o
> My code has been 32-bit only since I first wrote it, because I make use of
> the APIs in QuickTime/ImageCompression.h for encoding movies. It
Thanks everyone for your replies - some responses below:
On 5 Jul 2016, at 20:55, Greg Parker wrote:
> A synthesized property must use one of the following types of storage:
> 1. An ivar in that class that @synthesize creates.
> 2. An ivar in that class that you defined yourself.
>
> @synthesize
> On Jul 5, 2016, at 9:27 AM, Jens Alfke wrote:
>
>> On Jul 5, 2016, at 4:36 AM, Jonathan Taylor
>> wrote:
>>
>> It surprises me that I have to write different synthesis code for 32- or
>> 64-bit builds
>
> It’s because they use different Obj-C runtimes. For compatibility reasons,
> 32-bit
On Jul 5, 2016, at 04:36 , Jonathan Taylor
wrote:
>
> @interface ImmutableSettings : NSObject
> {
>BOOL_myFlag;
> }
> @property (readonly) BOOL myFlag;
> @end
>
> @interface MutableSettings : ImmutableSettings
> @property (readwrite) BOOL myFlag;
> @end
>
> @implementation ImmutableSet
> On Jul 5, 2016, at 4:36 AM, Jonathan Taylor
> wrote:
>
> It surprises me that I have to write different synthesis code for 32- or
> 64-bit builds
It’s because they use different Obj-C runtimes. For compatibility reasons,
32-bit Mac apps still use the old runtime, while 64-bit apps (and all
Thanks for that information - that’s very helpful. It sounds from what you are
saying as if there is nothing wrong with me redefining the *property* in the
subclass (as read-write), but that it’s just the synthesis itself that is the
problem? Assuming that is the case, I can easily(*) rectify th
> On Jul 5, 2016, at 5:36 AM, Jonathan Taylor
> wrote:
>
> I have a problem with property synthesis in my code, which I hope somebody
> can advise on. I find I have to write different property synthesis code for
> 32- or 64-bit builds in order to avoid compiler errors.
>
> A minimal demonstr
Hi all,
I have a problem with property synthesis in my code, which I hope somebody can
advise on. I find I have to write different property synthesis code for 32- or
64-bit builds in order to avoid compiler errors.
A minimal demonstration of the problem can be found below - build as part of a
12 matches
Mail list logo