> I use popen to fork and create the pipes between my parent and a
> spawned program. now popen returns a file * so i can simply do fprintfs to
> communicate with the spawn'd programs STDIN..
>
> however, this does not work.. popen will spawn the other program but it
> will not accept any input that I send to it from m y parent. Any ideas?
popen() is the wrong thing to use. You need to go through all the
fork(), exec(), and dup() stuff. A good reference for learning the
use of these mechanisms is _Advanced Programmming in the UNIX
Environment_ by Stevens. ISBN 0-201-56317-7. You *need* this book
(by "you" I mean anyone who is serious about Un*x programming, not
just Amit).
> Someone had mentioned "curses" ... does this ring a bell with anyone?
In this case, "curses" refers to the words you'll use when you find
out you've been chasing a red goose (or is that a wild herring?).
"curses" is a full screen "form" library which was designed for
creating user interfaces back in the VT100 terminal days. It's been
better than ten years since I've had to futz with "curses" and I grow
happier by the day that I don't have to futz with it any longer.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/