Parse list of? about argu HOT 10 CLOSED

It's possible, as long as you attach the [<Rest>] attribute to the corresponding parameter. So in your case,

type Params =
    | [<Rest>] Foo of string

which can then be used like so:

--foo string1 string2 string3

Note however, that Rest parameters should be placed at the end of your command line arguments, as they will consume all remaining tokens. I would find it safer -particularly if you plan to offer your application to other users- to simply use the following pattern, without the Rest attribute:

--foo string1 --foo string2 --foo string3

from argu.

So then I will get a string "string1 string2 string3" in the parse of Foo?

from argu.

Nope. You will be getting list of [ Foo "string1" ; Foo "string2" ; Foo "string3" ].

from argu.

And parser.GetResult <@ Foo @>? That's an array then?

from argu.

parser.GetResults <@ Foo @> gives you a list of strings.

from argu.

Thanks! =)

from argu.

Pleasure :)

from argu.

"Note however, that Rest parameters should be placed at the end of your command line arguments, as they will consume all remaining tokens."

I think it's not a very nice solution. I'd like the following to compile:

type Arg =
    | Hosts of string list
    | User of string
... 
parser.ParseCommandLine ([|"--hosts"; "h1"; "h2"; "h3"; "--user"; "u"|])

Is this hard to implement?

from argu.

I chose this way originally as it emulates the style of ArgParser in the
Powerpack. This is pretty straightforward to implement, but it comes with
certain ambiguity. For instance, how do you detect cases in which "--user"
was intended by the user as a host parameter? Weak argument, I know, but
keep in mind that it is possible to specify alternative identifiers for
each parameter that may lack the dash prefix.

Currently, the recommended way to specify multiple arguments is to use the
following style:
"--host host1 --host host2 --host host3"
This will still accumulate your parsed results in a list when you query
them and is a more idiomatic style command line argument scheme afaik.

On Wednesday, June 4, 2014, Vasily Kirichenko [email protected]
wrote:

"Note however, that Rest parameters should be placed at the end of your
command line arguments, as they will consume all remaining tokens."

I think it's not a very nice solution. I'd like the following to compile:

type Arg =
| Hosts of string list
| User of string... parser.ParseCommandLine ([|"--hosts"; "h1"; "h2"; "h3"; "--user"; "u"|])

Is this hard to implement?

—
Reply to this email directly or view it on GitHub
#4 (comment).

Sent from Gmail Mobile

from argu.

Now I agree that the current solution is OK. Thanks!

from argu.