From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: jyqvklioo@googlemail.com
Cc: emacs-devel@gnu.org
Subject: Re: Source Code Formatting Standard Update
Date: Wed, 16 Sep 2009 22:57:50 +0900 [thread overview]
Message-ID: <87k4zz0z6p.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <200909161356.26676.jyqvklioo@googlemail.com>
jyqvklioo@googlemail.com writes:
> I plea that the Standard be amended so that the { placement for the
> start of a body of a non-enclosed function is consistent with use
> otherwise.
-1
No thank you. Good standards are good, bad standards are bad,
changing standards are the worst. There is no strong reason to
change on the table, so let's not.
If you don't like the GNU standard, don't adopt it in your own
projects. At the start of a new cooperative project, argue for what
you consider a more rational standard. However, projects that have
followed it for a long time, including the whole GNU project, should
continue to do so unless a strong technical reason for changing can be
advanced. A little bit of extra work for automatic formatters and
those who write them is not such a reason.
> The increased consistency will also make it possible to have
> simpler implementations of automatic formatting software.
What could be simpler than to just let Emacs do it?
next prev parent reply other threads:[~2009-09-16 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 19:00 Source Code Formatting Standard Update jyqvklioo
2009-09-14 21:42 ` Stefan Monnier
2009-09-15 15:12 ` Richard Stallman
2009-09-16 11:56 ` jyqvklioo
2009-09-16 12:13 ` Alfred M. Szmidt
2009-09-16 13:33 ` jyqvklioo
2009-09-16 13:52 ` Alfred M. Szmidt
2009-09-16 14:08 ` Miles Bader
2009-09-16 13:57 ` Stephen J. Turnbull [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-15 5:53 jyqvklioo
2009-09-15 7:31 jyqvklioo
2009-09-15 7:39 ` Alfred M. Szmidt
2009-09-15 8:03 ` David Kastrup
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=87k4zz0z6p.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=jyqvklioo@googlemail.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.