so i updated this to work with nested arguments which is what i really
wanted to use it for in the first place. i almost always end up
creating a map of config settings and this makes it easy for me to
override things from the CL.
regarding the getopt stuff, i kind of agree but dont particularly l
I confess I didn't notice the type-conversion stuff in clargon; my
view is now basically the same as Miekel's: it's great to have these
new features, but they should be on top of getopt, which parses
excellently. In fact, I think I'll fork clargon and see if I can tweak
it that way.
On Dec 11, 1:3
Hi,
Am 11.12.2010 um 09:53 schrieb Saul Hazledine:
> I saw this and thought the opposite! I think it is a good thing that
> somebody has done a higher level argument parsing library.
>
> As far as I know, getopt doesn't support type conversion, help text or
> field validation. Generally, higher
On Dec 11, 7:08 am, Alan wrote:
> Have you considered instead providing a clojure wrapper around a well-
> known java command-line parser? The only one I've used is apache-
> commons-cli, which I found to be pretty lackluster,
> buthttp://www.freebsdsoftware.org/java/java-getopt.htmlis from FreeB
Have you considered instead providing a clojure wrapper around a well-
known java command-line parser? The only one I've used is apache-
commons-cli, which I found to be pretty lackluster, but
http://www.freebsdsoftware.org/java/java-getopt.html is from FreeBSD
and claims to be a 100% compatible po
oh hi,
i needed (well, wanted) a command line parser more like opt parser in
ruby so i threw one together:
https://github.com/gar3thjon3s/clargon
thought i would share in case anyone else finds it useful. im aware of
with-command-line but it didnt quite do what i wanted as i needed
functions tha
