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:32 am, Meikel Brandmeyer <[email protected]> wrote: > 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 level languages have better > > argument parsing libraries than the getopt style, Python for instance: > >http://docs.python.org/library/optparse.html > > This is completely orthogonal. Adding type conversion, help text or field > validation does not require the underlying parser to be re-implemented. One > can use getopt, commons-cli, with-command-line or jopt-simple and add things > on top for real added value. > > That said: I have no opinion about the posted code, because I haven't looked > at it, yet. Generally, I would prefer the above approach: use something > existing and add functionality on top. But then, I'm also guilty of > implementing a cli parser in Clojure myself. > > Sincerely > Meikel -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
