Re: Dynamic Method Creation
Re: Dynamic Method Creation
- Subject: Re: Dynamic Method Creation
- From: Alex Zavatone <email@hidden>
- Date: Sat, 15 Sep 2012 19:30:07 -0400
On Sep 15, 2012, at 7:20 PM, Jens Alfke wrote:
>
> On Sep 15, 2012, at 2:27 AM, Steve Steinitz <email@hidden> wrote:
>
>> Yes. I've "splayed" them because cocoa sometimes throws "cannot remove observer..." if you bind a value to x.y.z
>
> That’s a bug in your code, then — it probably means that your setX: or setY: methods aren’t posting KVO notifications.
>
>> Guys, I'd like to keep this thread focused on Dynamic Method Creation rather than my design deficiencies
>
> Why? Creating dozens of boilerplate methods is a bad workaround for a problem you shouldn’t need to be having.
It just seems to indicate that you could take a look at things and do it better.
Yes, this is a start that got you to this point, but sometimes, it's best to step back, look at what other people have to say, make sense of it, say "ohhhh, so I can do this then" and move on.
Dynamically creating methods when you should at least be thinking, "I can just have a data structure to be the day that the method can handle" seems like 2 steps away from what you should be doing if you're seriously considering making a proper stab at your problem.
Why dynamically create methods in the first place? Why do you want to do that and why do you think it's a good idea?
Cheers.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden