From: David Masterson <dsmasterson92630@outlook.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, stefankangas@gmail.com,
Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
juri@linkov.net
Subject: Re: Emacs-devel Digest, Vol 204, Issue 28
Date: Sun, 28 Feb 2021 22:04:43 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455D56F3A9E5724E6C1F4819B9A9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <E1lGFOK-0002EF-FD@fencepost.gnu.org> (Richard Stallman's message of "Sun, 28 Feb 2021 01:17:20 -0500")
Richard Stallman <rms@gnu.org> writes:
> [[[ 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. ]]]
>
> The reason we don't use braces in cases like this
>
> if (use_short_answers)
> {
> return call1 (intern ("y-or-n-p"), prompt);
> }
>
> is that the braces cause fewer real lines of code to fit on the
> screen. Because of that, they are not merely superfluous, they are an
> impediment to reading the code.
Different people look at it... differently. It probably depends on how
you were taught. I was taught C coding with the above style and my eye
is used to seeing the code structure this way. Remove the braces above
and it gets a little harder for me when you have a chain of these
if-thens.
--
David Masterson
next prev parent reply other threads:[~2021-03-01 6:04 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 [this message]
2021-03-02 13:11 ` Pedro Andres Aranda Gutierrez
2021-03-03 5:57 ` Richard Stallman
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=SJ0PR03MB5455D56F3A9E5724E6C1F4819B9A9@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson92630@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=paaguti@gmail.com \
--cc=rms@gnu.org \
--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 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.