unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
To: tantalum <sph@posteo.eu>
Cc: guile-user@gnu.org
Subject: Re: Long command line arguments using SRFI 37
Date: Sun, 6 Jan 2019 23:57:54 +0100	[thread overview]
Message-ID: <c4e17bc7-258f-2fa0-442b-306ac80c8276@gmail.com> (raw)
In-Reply-To: <2b163d77-a543-1715-b3ce-ed0d523c1b7a@posteo.eu>

On 1/6/19 1:07 PM, tantalum wrote:
> i dont know if it is possible, but the source code of srfi-37 is
> available, on my machine it is at
> /usr/share/guile/2.2/srfi/srfi-37.scm. i didnt see an option for the
> "--name value" case at first glance.
>
> apparently the --name=value syntax is to allow for long options with
> optional values. otherwise "--name value" and "value --name" might be
> ambiguous.
> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
>
> from the linked code:
>     ;; seed - What is the seed???
>
> seed is the initial value for what is "loads" in the code. it is the
> initial value for what eventually becomes the result of the call to
> args-fold. like the init parameter of fold.

I was wondering about that. So it's just that a fold needs an initial
value to work with. The names seed and loads are a bit difficult to make
sense of immediately, but I understand now.

Thanks!

Zelphir




  reply	other threads:[~2019-01-06 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 12:07 Long command line arguments using SRFI 37 tantalum
2019-01-06 22:57 ` Zelphir Kaltstahl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-04 18:55 Zelphir Kaltstahl
2019-01-04 20:04 ` Amirouche Boubekki
2019-01-05 13:22 ` Catonano
2019-01-07 14:08   ` Zelphir Kaltstahl

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=c4e17bc7-258f-2fa0-442b-306ac80c8276@gmail.com \
    --to=zelphirkaltstahl@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=sph@posteo.eu \
    /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).