Getoptlong, getopt, parseopt, which one to use for command linetool?

Use getopt for simple stuff or commandline if your needs are more
elaborate.

:smiley:

Dan

路路路

-----Original Message-----
From: ara.t.howard@noaa.gov [mailto:ara.t.howard@noaa.gov]
Sent: Friday, February 17, 2006 12:25 PM
To: ruby-talk ML
Subject: Re: getoptlong, getopt, parseopt, which one to use
for command linetool?

On Sat, 18 Feb 2006, Charlie Bowman wrote:

> There seems to be several options out there. Which one
should be used
> when creating command line tools?

it keeps things exciting to mix them up in unpredictable ways
- preferably in obfusicated code.

:wink:

seriously - use getoptlong for simple stuff and optparse if
your needs are more elaborate.

I'm not sure what you mean. I know what getopt is but what do you mean
by use commandline?

路路路

On Sat, 2006-02-18 at 04:38 +0900, Berger, Daniel wrote:

Use getopt for simple stuff or commandline if your needs are more
elaborate.

:smiley:

Dan

commandline is in RubyForge. See http://rubyforge.org/projects/optionparser/.

路路路

On 2/17/06, Charlie Bowman <charlie@castlebranch.com> wrote:

I'm not sure what you mean. I know what getopt is but what do you mean
by use commandline?

On Sat, 2006-02-18 at 04:38 +0900, Berger, Daniel wrote:

> Use getopt for simple stuff or commandline if your needs are more
> elaborate.
>
> :smiley:
>
> Dan
>

--
R. Mark Volkmann
Partner, Object Computing, Inc.