Re: Why can I not parse the command line arguments in this way

2014-04-23 Thread Atamert Ölçgen
On Tue, Apr 22, 2014 at 2:57 PM, Aaron France wrote: > One hates to be rude but: > > I've read all your questions over the past couple of weeks and it seems it > would behoove you to pick up a book. There are plenty of recommendations on > Google and archived threads. > Stackoverflow is also good.

Re: Why can I not parse the command line arguments in this way

2014-04-22 Thread Cecil Westerhof
2014-04-22 16:55 GMT+02:00 Moritz Ulrich : > This snippet is wholly incomplete. Can you please provide a more > complete, testable example as well as a detailed description of the > error you're seeing? > ​It was a stupid mistake of me. When making the following example: (defn -main [& args]

Re: Why can I not parse the command line arguments in this way

2014-04-22 Thread Aaron France
One hates to be rude but: I've read all your questions over the past couple of weeks and it seems it would behoove you to pick up a book. There are plenty of recommendations on Google and archived threads. Good day. On 22 Apr 2014 16:48, "Cecil Westerhof" wrote: > Obvious not very neat, but I t

Re: Why can I not parse the command line arguments in this way

2014-04-22 Thread Moritz Ulrich
This snippet is wholly incomplete. Can you please provide a more complete, testable example as well as a detailed description of the error you're seeing? On Tue, Apr 22, 2014 at 4:48 PM, Cecil Westerhof wrote: > Obvious not very neat, but I tried as a first hack to do something with the > command

Why can I not parse the command line arguments in this way

2014-04-22 Thread Cecil Westerhof
Obvious not very neat, but I tried as a first hack to do something with the command line parameters with: (doseq [type args] ​This does not work. Why not? ​ -- Cecil Westerhof -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this grou