• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
[Q] making IBOutlet property as weak : is it changed in Xcode 4.5.1?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Q] making IBOutlet property as weak : is it changed in Xcode 4.5.1?


  • Subject: [Q] making IBOutlet property as weak : is it changed in Xcode 4.5.1?
  • From: JongAm Park <email@hidden>
  • Date: Wed, 10 Oct 2012 14:03:46 -0700

Hello,

Since Xcode 4.5.1 I noticed a very interesting bug : When an IBOutlet is created by control-dragging to an interface file, it puts "_unsafe_unretained", although the small view for setting options for IBOutlet shows "weak". ( If you do not touch it, it will create "_unsafe_unretained", but if you touch the popup menu and choose "weak", it will create "weak" property. I filed this as a bug. )

Because I know that it is to be "weak" as it is described in "Patterns for Managing Outlets Become Consistent Across Platforms" within "Transitioning to ARC release notes", and because there was no problem in declaring and synthesizing IBOutlet that way until Xcode 4.5, I thought it would be OK to have them "weak" property.

However, after upgrading to Xcode 4.5.1, it started to show this message :

"Synthesis of a weak-unavailable property is disallowed because it requires synthesis of an ivar of the __weak object".

Just in case, I tried to declare the ivar as I had done with previous version of Xcode like Xcode 3.x,

@interface ....
{
	IBOutlet NSTextView * __weak textView; // with and without __weak in front of textView
}

Now it complains, "Class is incompatible with __weak reference."

So, it looks like that they are changing the required reference type for IBOutlet from weak to _unsafe_unretained.
I noticed that the error messages, "Synthesis of a weak-unavailable.. " was included in the last December code of LLVM.
Probably Apple people adopted it with Xcode 4.5.1 but failed in refine things around it?

Are there any other people who noticed this change? Can you share your idea if any?

Thank you.
JongAm Park
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: C++11 on Xcode 3.2.6 availablility
  • Next by Date: Re: XCode build gets stuck if simultaneously indexing
  • Previous by thread: Re: Can't build to an iOS device after upgrading drives.
  • Next by thread: Is There a Build Setting Relative to a Workspace?
  • Index(es):
    • Date
    • Thread