From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Committed initial (system* "foo" "bar") code.
Date: Fri, 21 Nov 2003 10:17:04 +1000 [thread overview]
Message-ID: <87d6bm8tj3.fsf@zip.com.au> (raw)
In-Reply-To: <87y8uc3tyz.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Wed, 19 Nov 2003 15:54:12 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
>
> The current version is careful to allocate the args before the fork,
> and follows the libc and perl convention of blocking SIGINT and
> SIGQUIT
For reference, what posix says on the subject can be found at
http://www.opengroup.org/onlinepubs/007904975/functions/system.html
> then make fixes as we figure out what else we need.
SCM_SYSERROR in the child will want to go I think, due to the way gtk
uses atexit, as discussed. _exit(127) might be a good idea until a
pipe to get the error back to the parent is introduced.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-11-21 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 21:54 Committed initial (system* "foo" "bar") code Rob Browning
2003-11-21 0:17 ` Kevin Ryde [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d6bm8tj3.fsf@zip.com.au \
--to=user42@zip.com.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).