ptyio / ptyspawn interface
"Laurent G. Bercot" <[email protected]> 4 Jun 2002 02:30:20 +0200
| Newsgroups | gmane.comp.lib.ptyget |
|---|---|
| Message-ID | <[email protected]> |
Hi, Forget about my last question, I finally figured out a way to do what I wanted without openpty(). This mail raises another question : I've studied the ptyget package rather deeply, and I'm still confused by ptyio and ptyspawn. There is an elaborated communication mechanism between ptyio and ptyspawn, which adds much complexity to ptyio's code, and forces ptyspawn to handle signals. Is all this really necessary, and if so, why ? The interface that comes naturally to my mind is something like : ptyget ptycopy program where ptycopy just makes the connection between stdin and the terminal's input, and between the terminal's output and stdout, a la ioconnect. (http://www.skarnet.org/software/conn-tools/ioconnect.html) But since Dan didn't make it that simple, there's probably a reason. What is it ? -- Ska