From: Mathieu Dube <mujo@dubix.org>
To: linux-c-programming@vger.kernel.org
Subject: Re: Getting output from another program.
Date: Wed, 21 Mar 2007 16:43:34 -0400 [thread overview]
Message-ID: <20070321204334.GB23547@dubix.org> (raw)
In-Reply-To: <46018F0A.9010801@cs.byu.edu>
On Wed, Mar 21, 2007 at 02:01:14PM -0600, Topher Fischer wrote:
> 2. What's the best practice for getting output from an external command?
> I've heard of it being done by forking, overwriting the child's file
> descriptors for stdin and stdout with pipes, and then exec'ing the
> command.
>
have you checked popen?
-M
prev parent reply other threads:[~2007-03-21 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 20:01 Getting output from another program Topher Fischer
2007-03-21 20:39 ` leslie.polzer
2007-03-21 20:43 ` Mathieu Dube [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070321204334.GB23547@dubix.org \
--to=mujo@dubix.org \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).