Re: assign property behaves differently from simple instance variable???

2010-12-14 Thread Matt Neuburg
On Mon, 13 Dec 2010 11:31:38 -0800, Wim Lewis w...@omnigroup.com said: On 13 Dec 2010, at 11:01 AM, Matt Neuburg wrote: How can this seemingly minor change make such a big difference? I'm not even *using* the synthesized accessor! Yet its mere presence breaks the project. How can this be? m.

Re: assign property behaves differently from simple instance variable???

2010-12-14 Thread Keary Suska
On Dec 13, 2010, at 12:01 PM, Matt Neuburg wrote: self-firstResponder = tf; Well, the proper syntax is self.firstResponder . Using the deference is probably a back-door way to access the class struct. Unless I misunderstand something Keary Suska Esoteritech, Inc. Demystifying

Re: assign property behaves differently from simple instance variable???

2010-12-14 Thread David Duncan
On Dec 14, 2010, at 10:01 AM, Keary Suska wrote: On Dec 13, 2010, at 12:01 PM, Matt Neuburg wrote: self-firstResponder = tf; Well, the proper syntax is self.firstResponder . Using the deference is probably a back-door way to access the class struct. Unless I misunderstand

Re: assign property behaves differently from simple instance variable???

2010-12-14 Thread Matt Neuburg
On Dec 14, 2010, at 10:01 AM, Keary Suska wrote: On Dec 13, 2010, at 12:01 PM, Matt Neuburg wrote: self-firstResponder = tf; Well, the proper syntax is self.firstResponder . Using the deference is probably a back-door way to access the class struct. Unless I misunderstand

Re: assign property behaves differently from simple instance variable???

2010-12-14 Thread Dave Keck
Hmm, also, it appears that UIResponder has some undocumented methods -firstResponder and -_firstResponder, which your synthesized property would also interfere with. Doubtless. But how would I have discovered this? I would have implemented -firstResponder and set a breakpoint to see who was

Re: assign property behaves differently from simple instance variable???

2010-12-14 Thread Kyle Sluder
On Dec 14, 2010, at 9:01 AM, Matt Neuburg m...@tidbits.com wrote: Doesn't anyone besides me want to evince any outrage that this can happen? I mean, sheesh, if I wanted to live in a world where the namespace was polluted with secret undocumented terminology I could collide with

assign property behaves differently from simple instance variable???

2010-12-13 Thread Matt Neuburg
I have reduced this problem (after losing an entire day of work, of course) to a very few lines of code. They won't make much sense but just bear with me. Here we go... I have this code (iOS), and it works fine: @interface TextFieldFunViewController : UIViewController { UIView*

Re: assign property behaves differently from simple instance variable???

2010-12-13 Thread Wim Lewis
On 13 Dec 2010, at 11:01 AM, Matt Neuburg wrote: How can this seemingly minor change make such a big difference? I'm not even *using* the synthesized accessor! Yet its mere presence breaks the project. How can this be? m. PS A new discovery: changing the name of the ivar / property to fr

Re: assign property behaves differently from simple instance variable???

2010-12-13 Thread Ricky Sharp
On Dec 13, 2010, at 1:31 PM, Wim Lewis wrote: On 13 Dec 2010, at 11:01 AM, Matt Neuburg wrote: How can this seemingly minor change make such a big difference? I'm not even *using* the synthesized accessor! Yet its mere presence breaks the project. How can this be? m. PS A new