+1 Using regular and proper formatting assists in submitting patches.
A little Javadoc would be nice as well. On Tue, Mar 24, 2009 at 4:46 AM, Mark Volkmann <r.mark.volkm...@gmail.com> wrote: > > +1 for running all the code under src/jvm through some code formatter > that uses something at least similar to the Sun Java conventions. > > On Mon, Mar 23, 2009 at 11:59 PM, BerlinBrown <berlin.br...@gmail.com> wrote: >> >> I was curious about how some of the clojure code worked and observed >> that the coding style is a little bit non idiomatic from typical Java >> coding conventions. E.g. there aren't any javadoc comments on methods >> or classes, non standard indents. >> >> Something like checkstyle might prove useful. >> >> http://checkstyle.sourceforge.net/ >> >> While, every programmer balks at conventions, I am sure there is a >> mountain of evidence for increased overall maintenance and other >> benefits. >> >> I know, I will get suggestions for clojure/lisp coding style. > > -- > R. Mark Volkmann > Object Computing, Inc. > > > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
