unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@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: Sat, 27 Feb 2021 09:50:39 -0500	[thread overview]
Message-ID: <jwvmtvp8t4a.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8335xiosc1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Feb 2021 09:58:06 +0200")

>> knowing in which context they are. So, those braces may be
>> 'superfluous' from the language point of view but they don't harm the
>> code and favour inclusiveness ;-)

That's indeed a good point, thanks.

> I removed those braces because they are against our coding style, not
> because of my personal preferences.

Looks like I need to go re-read our coding style ;-)
I mean, I know that we don't need those braces here and I don't put them
in the code I write (because they make my code too sparse for my taste),
but I didn't know our style was *against* their presence (rather than
merely allowing or even recommending their absence).


        Stefan




  parent reply	other threads:[~2021-02-27 14:50 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 [this message]
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

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=jwvmtvp8t4a.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --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).