Running it directly from the command-line (i.e. the second suggestion
above) will run it as a subprocess of your shell. This means that it
will inherit your shell's environment, and will have its stdin/out
attached to the same files as the shell itself, etc. *and* it will not
reactivate an already running instance of your app.
Yes, for sure this will act quite differently then an application
launched from the Finder. IMHO, having the stdin, stdout and std
error all attached to the terminal are extremely useful while
development. And the ability to set environment variables and have
them passed to the application is quite useful, especially if you're
having loader troubles (man dyld) and need to see what's going on.
Thanks for the clarification!
Mark
__
Mark Ritchie
Cocoa and WebObjects Developer
Diamond Lake Consulting Inc.
Toronto, Ontario, Canada
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
