It's all about priorities. At this point the goal is to write Clojure in 
Clojure, so the useful lifecycle of Java indentation fixes is hopefully modest.

If you are looking to spend time on Clojure, there are many tickets that need 
patches. :-)

https://www.assembla.com/spaces/clojure/tickets/custom_report/17449

Stu

> I get that. However, "broken" can describe code on several different levels, 
> not just on the level of compilation or execution.
> 
> I would say that for a young aspiring language like Clojure, having readable, 
> presentable source code is key, and that not having these things amounts to 
> being broken, no?
> 
> On 14 Oct 2010, at 10:47 pm, Santosh Rajan wrote:
> 
>> IMHO if it is not broken, dont fix it. I am sure the original authors are
>> aware and are very much around. Probably they would be the best people to do
>> it anyway.
>> 
>> On Fri, Oct 15, 2010 at 7:43 AM, David Jacobs <
>> develo...@allthingsprogress.com> wrote:
>> 
>>> I've just started learning Clojure and I'm excited about what I see. The
>>> combination of power and sophistication in the language is refreshing, and
>>> I've started to dive into the source code to understand it better.
>>> 
>>> One meta-observation has come out of my scouring.
>>> 
>>> The indentation used for the part of Clojure that's written in Clojure is
>>> beautifully indented, well documented, and generally easy to work through.
>>> On the other hand, the Java source doesn't look so consistent, either
>>> internally or with standard practices--especially as regards whitespace,
>>> indentation, and braces.
>>> 
>>> It may seem like a small thing, but I think that having well-formatted,
>>> consistent source code is important.
>>> 
>>> Would there be any objection to reformatting the Java source to make it
>>> consistent? I wouldn't mind undertaking that project in my free time.
>>> 
>>> Thoughts?
>>> 
>>> David
>>> 
>>> --
>>> 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
>>> Note that posts from new members are moderated - please be patient with
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@googlegroups.com<clojure%2bunsubscr...@googlegroups.com>
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>> 
>> 
>> 
>> 
>> -- 
>> http://hi.im/santosh
>> 
>> -- 
>> 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
>> Note that posts from new members are moderated - please be patient with your 
>> first post.
>> 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
> 
> -- 
> 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
> Note that posts from new members are moderated - please be patient with your 
> first post.
> 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

-- 
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
Note that posts from new members are moderated - please be patient with your 
first post.
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

Reply via email to