On 1/17/07, Zbigniew [EMAIL PROTECTED] wrote:
But you might have more success arguing that process should not ever
invoke a wait() call when you close its ports, and instead leave that
up to the user. Since you receive the PID from process, you can
process-wait on it, and retrieve the error
On Jan 17, 2007, at 11:54 PM, felix winkelmann wrote:
On 1/17/07, Kon Lovett [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
You can also try the osprocess egg. It will capture the exit status
when the ports are closed. Needs a current Chicken though, = 2.513
On 1/17/07, Robin Lee Powell [EMAIL PROTECTED] wrote:
On Sun, Jan 14, 2007 at 09:53:00PM -0800, Robin Lee Powell wrote:
The only way I see to get the exit value of something I call with
(process...) is to use (process-wait), but as I mentioned in another
mail, this errors out my entire
On Wed, Jan 17, 2007 at 11:26:27AM +0100, felix winkelmann wrote:
On 1/17/07, Robin Lee Powell [EMAIL PROTECTED] wrote:
On Sun, Jan 14, 2007 at 09:53:00PM -0800, Robin Lee Powell wrote:
The only way I see to get the exit value of something I call
with (process...) is to use (process-wait),
Robin,
Did you try using process-fork to create the process, as Felix
suggested? The process can't end until you actually call
process-wait. In fact, you normally should call process-wait to
properly reap your children. If you are noticing your children are
being reaped automatically on your
On Wed, Jan 17, 2007 at 01:45:03PM -0600, Zbigniew wrote:
Robin,
Did you try using process-fork to create the process, as Felix
suggested? The process can't end until you actually call
process-wait.
*hangs head*
You know, I knew that, I really did.
I'll give it a shot.
I the meantime,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
You can also try the osprocess egg. It will capture the exit status
when the ports are closed. Needs a current Chicken though, = 2.513
Best Wishes,
Kon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
I would agree with Kon on this---osprocess should work and give you
more options. To me the overall problem is that opening both a read
and write pipe to a process contains a bit of magic, and is not as
easy as one might suppose. For example, many times you are better
opening a pseudo tty,
Zbigniew scripsit:
But you might have more success arguing that process should not ever
invoke a wait() call when you close its ports, and instead leave that
up to the user. Since you receive the PID from process, you can
process-wait on it, and retrieve the error code yourself. This way,
On 1/17/07, John Cowan [EMAIL PROTECTED] wrote:
What do people think? Should the wait() be removed from process?
Yes, I'd say so; it's not hard to insert a call to wait right after
closing the input port.
Note that Perl behaves this way w/r/t bi-directional pipes as well,
requiring an
On 1/17/07, Kon Lovett [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
You can also try the osprocess egg. It will capture the exit status
when the ports are closed. Needs a current Chicken though, = 2.513
Kon, would it be possible to isolate the code for
On Sun, Jan 14, 2007 at 09:53:00PM -0800, Robin Lee Powell wrote:
The only way I see to get the exit value of something I call with
(process...) is to use (process-wait), but as I mentioned in another
mail, this errors out my entire program if the process is already
finished, so I can't see
The only way I see to get the exit value of something I call with
(process...) is to use (process-wait), but as I mentioned in another
mail, this errors out my entire program if the process is already
finished, so I can't see any way to do all of the following:
1. Call process
2. Read and
13 matches
Mail list logo
