> On Jun 29, 2015, at 1:19 PM, Scott Ribe <scott_r...@elevated-dev.com> wrote: > >> The problem with the callback to “after” is that “after” is just the >> continuation of the program and possibly nothing to do with what happens in >> “fakeSyncrony” .. > > Then why does it need to wait? > > This is really sounding like program behavior that is poorly specified.
.. I can’t speak to that, it’s not my program and I’ve never seen the code. I’m trying to help the author, but I have to describe the issue in general terms and I’m sure I’m doing him an injustice. I haven’t given any information that would allow you to be specific in your answers, but it’s really not my intention to frustrate .. my original, general question is the best statement, and the allowance for trickery is the word “apparently”. Q: “Can anyone suggest a trick that allows an apparently synchronous call on the main thread without impacting performance?” A: “Yes, here are some possibilities, but they are difficult and dangerous, and you should find a better way (with suggestions).” That is a satisfactory response, and provides food for thought. This is the best forum I know; others have too many people who don’t read the question carefully, and guess at answers. The “cocoa-dev@lists.apple.com” list has people on it who I have respected for decades. I’ve read it for ever because gems drop from your keyboards. So, since I’m typing anyway, I’ll take the opportunity to thank you for that over the years, and for this today. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
