From: Barry Margolin <barry.margolin@level3.com>
Subject: Re: Lisp code formatting....
Date: Fri, 07 Mar 2003 21:49:43 GMT [thread overview]
Message-ID: <Xt8aa.18$LF5.1550@paloalto-snr1.gtei.net> (raw)
In-Reply-To: b607d812.0303071225.576996cb@posting.google.com
In article <b607d812.0303071225.576996cb@posting.google.com>,
Sandip Chitale <sandipchitale@yahoo.com> wrote:
>I was reading through the emacs lisp manual and came across the
>following paragraph:
>
> * Don't make a habit of putting close-parentheses on lines by
> themselves; Lisp programmers find this disconcerting.
>
>Why do "Lisp programmers find this disconcerting" ? Do *all* Lisp
>programmers find this disconcerting ? I don't.
The majority of people with several decades of experience. We learned the
standard programming style from each other, just like other idioms of the
language.
> Once in a while, when there is a sequence of many consecutive
> close-parentheses, it may make sense to split the sequence in one
> or two significant places.
>
>Isn't this arbitrary ? It does not sound like a standard.
>
>Can Emacs lisp gurus shed some light on this ?
Since there are so many parentheses in Lisp code, devoting a line to each
close paren wastes lots of space and clutters up the definition.
Parentheses tend to be viewed as noise, so they shouldn't be emphasized so
much. While the Lisp implementation cares about them quite a bit,
programmers tend to depend on indentation to see the structure of the code.
And editors like Emacs automate the indentation process.
--
Barry Margolin, barry.margolin@level3.com
Genuity Managed Services, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
next prev parent reply other threads:[~2003-03-07 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 20:25 Lisp code formatting Sandip Chitale
2003-03-07 21:49 ` Barry Margolin [this message]
2003-03-08 14:25 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Xt8aa.18$LF5.1550@paloalto-snr1.gtei.net' \
--to=barry.margolin@level3.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.