From: "Eric J. Roode" <sdn.girths00869@...>
Date: 2005-12-29T07:52:54+09:00
Subject: Re: Command-line option parsing

mathew <meta@pobox.com> wrote in news:wjosf.9901$9e.8623
@tornado.texas.rr.com:

> Eric J. Roode wrote:
>> GetoptLong suffers from being "the same old Getopt".  
> 
> Well, what do you expect from an options parser?  It's pretty much a 
> solved problem, and using the standard getopt algorithms has the 
> advantage that users know what to expect.

Well... that's not *bad*, but I guess I had expected something a bit more 
ruby-like.  Whatever that means.  :-)


-- 
Eric
`$=`;$_=\%!;($_)=/(.)/;$==++$|;($.,$/,$,,$\,$",$;,$^,$#,$~,$*,$:,@%)=(
$!=~/(.)(.).(.)(.)(.)(.)..(.)(.)(.)..(.)......(.)/,$"),$=++;$.++;$.++;
$_++;$_++;($_,$\,$,)=($~.$"."$;$/$%[$?]$_$\$,$:$%[$?]",$"&$~,$#,);$,++
;$,++;$^|=$";`$_$\$,$/$:$;$~$*$%[$?]$.$~$*${#}$%[$?]$;$\$"$^$~$*.>&$=`