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 states many of these conventions which are
rarely spelled out explicitly
- attempts to explain some of the conventions that can be mystifying at
first
- offers genuinely good readability and maintenance reasons for some of
the mentioned conventions
but please, don't mis-understand my intentions, I see nothing wrong with
personal coding idosynchronies, I myself have been known to drop the
occasional
((fn [el]
(body-which-uses el))
(form-which-defines-el))
just because I've grown tired of `let'. That said even if you don't
follow common conventions it can be useful to know what they are.
Sorry for troll baiting, it was not my intent. -- Eric
Greg <g...@kinostudios.com> writes:
> 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 wars"
> - Animosity amongst members of the group
> - Noise on the channel
> - The fostering of a militant, "prickly" community (i.e. the one that LISP is
> famous for)
>
> Clojure is an opportunity to depart from all of that.
>
> - Greg
>
> On Aug 31, 2010, at 1: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 (not all
>> parenthesis must be trailed), but the so-called rationale given for choosing
>> stacked parens over trailed parens is laughably devoid of any rational
>> thought:
>>
>>> Rationale: The parentheses grow lonely if their closing brackets are
>>> all kept separated and segregated.
>>
>>
>> - Greg
>>
>> On Aug 31, 2010, at 9:47 AM, Eric Schulte wrote:
>>
>>> This is the best I've seen so I thought I'd share
>>> (pulled from a post on the guile mailing list)
>>>
>>> http://mumble.net/~campbell/scheme/style.txt
>>>
>>> (note: the attached copy opens in Org-mode in Emacs for easier reading)
>>>
>>> --
>>> 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<style.txt>
>>
>> --
>> 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
