Re: Using NSThreads in command-line apps
Re: Using NSThreads in command-line apps
- Subject: Re: Using NSThreads in command-line apps
- From: Randall Meadows <email@hidden>
- Date: Thu, 15 May 2008 12:49:43 -0600
On May 15, 2008, at 12:42 PM, ben syverson wrote:
I have a bit of a dilemma. I'm working on a Foundation-based command-
line utility that needs to manage a few threads. The obvious choice
is NSThread, since it's nice and clean.
Actually, I'm able to spawn new threads perfectly well. The problem
is that I can't (?) use performSelectorOnMainThread: because I'm not
an NSApplication, and so I don't get the default "main" thread that
loops for user input...
Am I busted? I would like to be able to run this app without the
window server running (ie, in Single User Mode), because it's server
software.
I can always fall back to POSIX threads, but I'd rather use NSThread
if possible. Is there an alternate way to have my spawned NSThreads
call back to a controller thread (that doesn't require 10.5)?
Can't you cache the main thread [NSThread +currentThread] when you
start up, and then use NSObject's -
performSelector:onThread:withObject:waitUntilDone: method?
_______________________________________________
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