Re: code-completion in 1.5 buggy? (2)
Re: code-completion in 1.5 buggy? (2)
- Subject: Re: code-completion in 1.5 buggy? (2)
- From: Shawn Erickson <email@hidden>
- Date: Thu, 19 Aug 2004 10:30:21 -0700
On Aug 19, 2004, at 9:26 AM, Izidor Jerebic wrote:
On 19 Aug 2004, at 17:30, Scott Thompson wrote:
On Aug 19, 2004, at 7:33 AM, Izidor Jerebic wrote:
Well, I have got an interesting example. In the following code, in
the first line (if) everything works for "item", but in the second
line (else) the completion does not work for "item" (e.g. deleting
last 'e' from valueForAttribute and asking for the completion). This
code compiles just fine. Suggestions?
if( ![item hasAttribute:@"test"] ) i++ ;
else i += [[item valueForAttribute:@"test"] intValue] ;
izidor
Not that it's a good general solution, but try the following just to
see what happens:
In front of "item" put a typecast operator that explicitly identifies
the type of "item"
So if item is declared as "MyWhizzyType *item", try changing your
line to:
else i += [[(MyWhizzyType *)item valueForAttribut<cursor here>
and see if the code completion works better. If it does, that may
help you formulate a bug report.
It does not. But if I remove the 'else' or put the statement in the
next line then code completion works. Funny, isn't it?
I guess it's time to bugreport.apple.com...
Well maybe it is time to change you coding style to something readable
;-)
-Shawn
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.