On 21/08/2013, at 12:59 AM, Gerriet M. Denkmann wrote:
>> What version of Xcode? I just tried this with Xcode 4.6.3 and it worked
>> perfectly.
>
> A difficult question: I am not allowed to talk about this (which might give
> you an idea, which version I was using).
Worked fine for me in an
Actually, I think the question is "what version of Xcode are you upgrading the
project from and what version of Xcode are you using to do the conversion?"
That way, it's much easier to pin down the specific case that might be causing
this.
- Alex Zavatone
On Aug 20, 2013, at 10:57 AM, glenn
On 20 Aug 2013, at 21:54, glenn andreas wrote:
>
> On Aug 20, 2013, at 8:43 AM, Gerriet M. Denkmann wrote:
>
>>
>> On 20 Aug 2013, at 20:27, Fritz Anderson wrote:
>>
>>> Sure, but the whole point the OP is trying to make is that the purported
>>> error is being raised by the refactoring p
On Aug 20, 2013, at 8:43 AM, Gerriet M. Denkmann wrote:
>
> On 20 Aug 2013, at 20:27, Fritz Anderson wrote:
>
>> Sure, but the whole point the OP is trying to make is that the purported
>> error is being raised by the refactoring process that is _supposed to remove
>> that retain_. Refactor
On 20 Aug 2013, at 21:41, Jens Alfke wrote:
> This looks like a bug in Xcode’s refactoring tool — seems it doesn’t
> understand the auto-synthesize feature. I would take your test case and
> attach it to a new Radar bug report to Apple.
Just done this. Bug 14784266.
Gerriet.
_
This looks like a bug in Xcode’s refactoring tool — seems it doesn’t understand
the auto-synthesize feature. I would take your test case and attach it to a new
Radar bug report to Apple.
The workaround should be to add an explicit instance variable declaration and
an “@synthesize” directive whe
On 20 Aug 2013, at 20:27, Fritz Anderson wrote:
> Sure, but the whole point the OP is trying to make is that the purported
> error is being raised by the refactoring process that is _supposed to remove
> that retain_. Refactoring would be a very easy process indeed if doing the
> conversion y
Sure, but the whole point the OP is trying to make is that the purported error
is being raised by the refactoring process that is _supposed to remove that
retain_. Refactoring would be a very easy process indeed if doing the
conversion yourself is a prerequisite of having Xcode do it.
The use o
On 20/08/2013, at 9:07 PM, "Gerriet M. Denkmann" wrote:
> How to placate Xcode?
Are you sure it's not the use of retain that it's complaining about? Without
that, your code compiles fine here.
--
Shane Stanley
'AppleScriptObjC Explored'
___
Coc
On 20 Aug 2013, at 19:24, Uli Kusterer wrote:
> You're missing an @synthesize privateData = _privateData; in your
> @implementation, would be my guess.
There is no @synthesize, this is true.
But Xcode normally does not mind, and I think this is (since when?) no longer
necessary (maybe only i
You're missing an @synthesize privateData = _privateData; in your
@implementation, would be my guess.
On Aug 20, 2013, at 1:07 PM, Gerriet M. Denkmann wrote:
> Trying to convert an older project to Arc, Xcode complains about "Use of
> undeclared identifier '_privateDate'".
> And threatens that
Trying to convert an older project to Arc, Xcode complains about "Use of
undeclared identifier '_privateDate'".
And threatens that nothing will be done unless I fix this first.
Well - for one: without Arc there are no undeclared identifiers. (Builds
without error or warnings).
The class with pr
12 matches
Mail list logo
