From: Richard Stallman <rms@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel@gnu.org, stefankangas@gmail.com,
dsmasterson92630@outlook.com, juri@linkov.net
Subject: Re: Emacs-devel Digest, Vol 204, Issue 28
Date: Wed, 03 Mar 2021 00:57:49 -0500 [thread overview]
Message-ID: <E1lHKW5-0006a6-RK@fencepost.gnu.org> (raw)
In-Reply-To: <FFCCEEB4-0D78-45EE-93E1-BDE069CC39BE@gmail.com> (message from Pedro Andres Aranda Gutierrez on Tue, 2 Mar 2021 14:11:21 +0100)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I was talking about visually impaired people who use tts and,
> frankly speaking, a brace stands out much more than an
> indentation. The feedback I have is explicit braces are helpful
> for them when reading through the code.
To put braces around every one-line conditional body would have
advantages and disadvantages. I think the disadvantages would
outweigh the advantages, so we should stick with the current coding
conventions.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2021-03-03 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.35.1614358824.18242.emacs-devel@gnu.org>
2021-02-27 7:48 ` Emacs-devel Digest, Vol 204, Issue 28 Pedro Andres Aranda Gutierrez
2021-02-27 7:58 ` Eli Zaretskii
2021-02-27 11:34 ` Pedro Andres Aranda Gutierrez
2021-02-27 14:50 ` Stefan Monnier
2021-02-27 14:59 ` Eli Zaretskii
2021-02-28 6:17 ` Richard Stallman
2021-03-01 6:04 ` David Masterson
2021-03-02 13:11 ` Pedro Andres Aranda Gutierrez
2021-03-03 5:57 ` Richard Stallman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1lHKW5-0006a6-RK@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dsmasterson92630@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=paaguti@gmail.com \
--cc=stefankangas@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).