From: ludo@gnu.org (Ludovic Courtès)
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: "exec" procedures don't handle the optional parameters unbounded situation?
Date: Sat, 17 Dec 2011 00:02:18 +0100 [thread overview]
Message-ID: <87r504unlx.fsf@gnu.org> (raw)
In-Reply-To: <CAPjoZoemjo7HArNgsBGFb2SUF+3RMtVm1XOoU+UF-ryh92fQnQ@mail.gmail.com> (Nala Ginrut's message of "Fri, 16 Dec 2011 12:03:50 +0800")
Hello!
Nala Ginrut <nalaginrut@gmail.com> skribis:
> Since Guile provides flexible optional arguments handling, why we can not
> do this:
> let (execlp "ls") equal to (execlp "ls" "") if the second argument is
> unbounded?
Because it would differ from what the underlying system call allows, and
would also be an incompatible change.
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-12-16 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 9:24 "exec" procedures don't handle the optional parameters unbounded situation? Nala Ginrut
2011-12-15 19:19 ` Ludovic Courtès
2011-12-16 4:03 ` Nala Ginrut
2011-12-16 23:02 ` Ludovic Courtès [this message]
2011-12-17 4:34 ` David Kastrup
2012-01-06 18:02 ` Andy Wingo
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=87r504unlx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@gmail.com \
/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).