An interesting candidate for this is the current
clojure.contrib.pprint tool. It should be adapted to not only grok
clojure forms, but also strings, of course (and this may not be that
easy), so that nothing in the source code is lost during the parsing
...
2010/9/6 :
> It would be _nice_ to have
It would be _nice_ to have a default that was the baseline format. The Canon of
Clojure Conventional Conformity ().
If an org or project wanted to have a different format, they could supply it as
a plugin to the clojure-fmt tool.
(set-format "local-conventions")
When the format gets applie
>
> I think it would be great if an official "clojure-fmt" tool existed.
> I have no interest in forcing people to use it who don't want to. But
> I think it would set a great baseline for IDEs and would be helpful to
> the people and teams who like having coding standards. I would be one
> of a
On Sun, Sep 5, 2010 at 1:08 PM, Daniel Gagnon wrote:
> I'd be all for having clojure-fmt that would format clojure code in the way
> Rich prefers it so that when I get random code I could convert it to a nice
> and predictable format. It should be even simpler to write for a lisp than
> other lang
> I'd be all for having clojure-fmt that would format clojure code
> in the way Rich prefers it so that when I get random code I could
> convert it to a nice and predictable format. It should be even
> simpler to write for a lisp than other languages.
See Guy Steele "Common Lisp, The Language" pp
>
>a) Python doesn't really have this problem
>
Python doesn't have this problem because the canonical style is define by
PEP 8 and Pythonistas love simplicity through conventions.
PEP 8: http://www.python.org/dev/peps/pep-0008/
I think it's actually a great feature of the language, I almost
In an effort to paint the shed until it crumbles I will stoke the engine of
discourse with starter fluid.
I see a couple issues that probably *should* be resolved within the community
and once resolved can be pointed to as Canon of
Clojure Conventional Conformity ().
bla bla wadler's law ..
In an effort to paint the shed until it crumbles I will stoke the engine of
discourse with starter fluid.
I see a couple issues that probably *should* be resolved within the community
and once resolved can be pointed to as Canon of
Clojure Conventional Conformity ().
bla bla wadler's law .
I'm afraid if I write my code while this thread is going on, I'll just
have to reformat all of it once the discussion has settled this
decades-old argument.
On Sep 1, 9:45 am, ataggart wrote:
> This is so terribly boring. Don't you guys have any code to write?
--
You received this message beca
On Sep 1, 2010, at 9:45 AM, ataggart wrote:
> This is so terribly boring. Don't you guys have any code to write?
A similar question may be asked of you.
Do you not have anything better to do than complain?
If you find this thread boring, why are you 1) reading it, and 2) replying to
it and th
This is so terribly boring. Don't you guys have any code to write?
--
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 y
On Sep 1, 2010, at 8:33 AM, David Nolen wrote:
> Comparing code formatting to painting practice is a poor metapor at best.
The comparison is between programming and painting. Code formatting is being
compared to the various artistic decisions involved in painting.
I think it is a very apt metap
On Wed, Sep 1, 2010 at 11:07 AM, Greg wrote:
> Fogus, I believe it is you who is confused.
>
> The painter is responsible for everything about the painting. Where the
> brush strokes are placed, how they are used, the medium that is used, the
> brush widths, and everything else. If his point was
Fogus, I believe it is you who is confused.
The painter is responsible for everything about the painting. Where the brush
strokes are placed, how they are used, the medium that is used, the brush
widths, and everything else. If his point was to paint a bridge he could have
done it through a var
I guess much of this comes down to style. I find xml-http-request easier to
read and consistent with the english language practice of using hyphens to join
words in compound modifiers.
But my point regarding XMLHttpRequest was regarding the seemingly arbitrary and
difficult to remember (for me
On Tue, Aug 31, 2010 at 3:38 PM, Cyrus Harmon wrote:
> XMLHttpRequest vs. xml-http-request. I rest my case.
I'm not even sure what case you're making, let alone what side you're
"resting" for. :-/
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To
On Tue, Aug 31, 2010 at 1:52 PM, Greg wrote:
> Can we please drop this?
No offense Greg, but yes, please, drop this.
By replying, all you've done is perpetuate this :(
It's clear you don't agree (with lots of other people's opinions) and
we get that. Style is personal - do what makes you happy.
> It would be a tragedy if The State ordered Picasso to make his paintings more
> realistic
I think your confusing the virtue in shuffling parentheses around. If
you want to place your parentheses on their own line then more power
to you, it's your style -- but don't confuse it with making high
On Aug 31, 2010, at 5:26 PM, Mike Meyer wrote:
> Um, read the explanation: he's talking about productivity and code
> quality. He didn't say people didn't care about styles, or weren't
> passionate about styles. Which means you haven't addressed his issues,
> just your straw man.
There is no stra
On Tue, 31 Aug 2010 15:41:13 -0700
Greg wrote:
> On Aug 31, 2010, at 2:35 PM, fin wrote:
>
> >> The concept of the One-Style-To-Rule-Them-All is just childish.
> >
> > Have you read "Style is Substance"?
> > http://www.artima.com/weblogs/viewpost.jsp?thread=74230
>
> No, I hadn't, thanks for t
On Tue, 31 Aug 2010 15:40:10 -0600
"Eric Schulte" wrote:
> I apologize for apparently re-opening some fresh wounds.
>
> I wasn't trying to assert that these guidelines should be universally
> adopted or enforced.
>
> There are a number of conventions that exist for writing lisp, and I
> thought
On Aug 31, 2010, at 2:35 PM, fin wrote:
>> The concept of the One-Style-To-Rule-Them-All is just childish.
>
> Have you read "Style is Substance"?
> http://www.artima.com/weblogs/viewpost.jsp?thread=74230
No, I hadn't, thanks for the link.
I tried to read the whole thing but stopped after readi
XMLHttpRequest vs. xml-http-request. I rest my case.
On Aug 31, 2010, at 3:35 PM, Mark Engelberg wrote:
> Speaking of style conventions, am I the only one who finds it mildly
> irksome that in any Clojure code, half the identifiers are
> lisp-style-multiword-names while the other half are
> javaC
Speaking of style conventions, am I the only one who finds it mildly
irksome that in any Clojure code, half the identifiers are
lisp-style-multiword-names while the other half are
javaCamlCaseMethodNames. It feels so inconsistent.
I'd be happier if Clojure just moved completely to caml case (take
I apologize for apparently re-opening some fresh wounds.
I wasn't trying to assert that these guidelines should be universally
adopted or enforced.
There are a number of conventions that exist for writing lisp, and I
thought that this paper was interesting because it
- collects and explicitly sta
On Tue, Aug 31, 2010 at 4:52 PM, Greg wrote:
> Can we please drop this?
>
> This is going to go nowhere fast, like other thread on closing parens on new
> lines.
>
> Whoever wrote this did a terrible job, at least WRT that topic.
>
> Not only did he misrepresent the trailing parenthesis style (no
> The concept of the One-Style-To-Rule-Them-All is just childish.
Have you read "Style is Substance"?
http://www.artima.com/weblogs/viewpost.jsp?thread=74230
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure
The concept of the One-Style-To-Rule-Them-All is just childish.
It is akin to the enforcement of school uniforms, and in many ways perhaps
worse.
The imposition of aesthetic preferences upon others is likely to result in the
following:
- A counter-reaction, such as argument, insults, "flame wa
Can we please drop this?
This is going to go nowhere fast, like other thread on closing parens on new
lines.
Whoever wrote this did a terrible job, at least WRT that topic.
Not only did he misrepresent the trailing parenthesis style (not all
parenthesis must be trailed), but the so-called rati
29 matches
Mail list logo
