From: ludo@gnu.org (Ludovic Courtès)
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: guile-devel@gnu.org
Subject: Re: EXIT_SUCCESS and EXIT_FAILURE in scheme land
Date: Mon, 22 Sep 2014 22:53:29 +0200 [thread overview]
Message-ID: <877g0vl6ly.fsf@gnu.org> (raw)
In-Reply-To: <87a96c67xs.fsf@ft.bewatermyfriend.org> (Frank Terbeck's message of "Sat, 06 Sep 2014 18:16:15 +0200")
Frank Terbeck <ft@bewatermyfriend.org> skribis:
> I personally don't know any OS that doesn't use EXIT_SUCCESS := 1, but
> nevertheless I think it's useful to have EXIT_SUCCESS and _FAILURE
> available in scheme land. They are from stdlib.h, so I suppose adding
> them to ‘libguile/posix.c’ makes sense. The patch below seems to do the
> trick for me.
>
> Would something like this be welcome?
Yes (esp. since the GNU Coding Standards suggest using them.)
Pushed as 447af51.
Thanks,
Ludo’.
prev parent reply other threads:[~2014-09-22 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 16:16 EXIT_SUCCESS and EXIT_FAILURE in scheme land Frank Terbeck
2014-09-07 14:02 ` Frank Terbeck
2014-09-22 20:53 ` Ludovic Courtès [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=877g0vl6ly.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ft@bewatermyfriend.org \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).