Hi Zelphir,
Just as a heads up — this is perhaps a little tangential. I created the
guile-config package
(https://gitlab.com/a-sassmannshausen/guile-config), which builds on
getopt-long to provide a (IMHO) richer and more sustainable approach to
managing commandline options for a program.
Just
On 09.07.2018 05:42, Keith Wright wrote:
> Actually my copy of the manual says:
> (predicate func)
> ...
> then getopt-long will apply func to the value,
> and throw an exception if it returns #f.
>
> func should be a procedure which accepts a string and
> returns a
Zelphir Kaltstahl writes:
>>> I decided to take a look at how one can parse command line arguments in
>>> Guile and was looking for something like argparse in Python. It seems
>>> that (use-modules (ice-9 getopt-long)) does the job, except that I hit
>>> one problem and don't know what the
On 07/08/2018 10:00 AM, Zelphir Kaltstahl wrote:
On 08.07.2018 18:00, guile-user-requ...@gnu.org wrote:
Apart from this issue, what are the reasons for SRFI-37 to be
recommended over getopt-long?
The reason I changed was that I wanted to handle multiple flagged
arguments (e.g, "-x abc -x
On 08.07.2018 18:00, guile-user-requ...@gnu.org wrote:
> --
>
> Message: 3
> Date: Sun, 8 Jul 2018 08:44:22 -0700
> From: Matt Wette
> To: guile-user@gnu.org
> Subject: Re: Parsing command line arguments, predicate error
> Message-ID:
> Content-Type: text/plain;
