Re: exec(uting) Safari - How (newbie)
Re: exec(uting) Safari - How (newbie)
- Subject: Re: exec(uting) Safari - How (newbie)
- From: Jason Coco <email@hidden>
- Date: Wed, 2 Jul 2008 00:45:14 -0400
What env pollution? I agree that exec* isn't really the way to go, but
that's what the OP was using... I just suggested that /usr/bin/open is
a better option than hard-coding the path to some arbitrary
application. It's also a lot easier to use than the LaunchServices
API... although if I were gonna use it, I'd definitely do so from an
NSTask object as others have already suggested.
On Jul 1, 2008, at 23:44 , Kyle Sluder wrote:
On Tue, Jul 1, 2008 at 8:17 PM, Kevin Elliott <email@hidden>
wrote:
Of course, they're both bad choices. As several people have
pointed out,
NSWorkspace launchApplication or openURL depending on the
requirements. If
it's not possible to use NSWorkspace (i.e. because you can't link
against
AppKit) consider NSTask or using LaunchServices. But unless you
have a
SPECIFIC, low level requirement exec is the wrong API.
I was even more concerned about the env pollution necessary for exec
to work as described ("not needing to know where Safari lives"). exec
is just a bad idea all around for anything outside of the BSD
environment.
--Kyle Sluder
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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