Re: crash-proof AU plugin scanning?
Re: crash-proof AU plugin scanning?
- Subject: Re: crash-proof AU plugin scanning?
- From: Kyle Sluder <email@hidden>
- Date: Wed, 30 Jun 2010 08:22:54 -0700
On Jun 30, 2010, at 12:25 AM, Brian Willoughby <email@hidden> wrote:
> If you want access to the actual textual output of the command-line process, then use popen(3) and pclose(3), documented as part of <stdio.h> These API give you bidirectional pipe forking, so you can write to the process (not needed for auval) and read from the process (probably useful for scanning results for particular text, although that might be a weak approach given that auval could change in the future).
Avoid using system(3). There's no good reason to invoke a shell and introduce all the security implications that entails. Really, that API should be discarded.
Cocoa has a convenient API called NSTask that you can use to invoke external utilities. It avoids the pitfalls of using a shell when all you want to do is launch a helper process.
--Kyle Sluder _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden