Yes, I’m being lazy.
What happens when I call performSelector:onThread:... and pass in a thread that’s currently blocked (on synchronous I/O, for instance)? Does the selector just get queued to be executed later?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Yep. I’m pretty sure it gets added to the thread’s runloop so it will be performed on the next iteration.