all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] xwidget 9fe732a 2/2: Better changelog for xwidgets
Date: Mon, 09 Feb 2015 14:20:25 -0800	[thread overview]
Message-ID: <54D932A9.1020004@cs.ucla.edu> (raw)
In-Reply-To: <m3sieen893.fsf@exodia.verona.se>

On 02/09/2015 12:24 PM, joakim@verona.se wrote:
> My concern was that I have made no changees AFAIK to coding.c. So how
> did it wind up in the patch you provided?

I don't recall, but let's not worry about it.

>
>>> >>And these:
>>> >>-  next_element_from_stretch
>>> >>+  next_element_from_stretch,
>>> >>   #ifdef HAVE_XWIDGETS
>>> >>-  ,next_element_from_xwidget
>>> >>+  next_element_from_xwidget,
>>> >>
>>> >>is it really correct to move the coma out of the ifdef?
>> >
>> >Yes, in C99, which Emacs is now assuming.
> It feels weird, but well okay then. And its really considered better
> form?
>

I prefer it, because it lets one put #if/#endif brackets around any enum 
value without worrying about whether the value is listed first or last 
or in the middle.  The style with leading "," is less consistent, in 
that it cannot be used with the first enum value.



  reply	other threads:[~2015-02-09 22:20 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150201003025.18138.95966@vcs.savannah.gnu.org>
     [not found] ` <E1YHiQk-0004jf-UH@vcs.savannah.gnu.org>
2015-02-01  6:11   ` [Emacs-diffs] xwidget 9fe732a 2/2: Better changelog for xwidgets Dmitry Gutov
2015-02-01  8:50     ` joakim
2015-02-01 10:53       ` Paul Eggert
2015-02-01 15:46         ` joakim
2015-02-01 16:09           ` Dmitry Gutov
2015-02-01 16:17             ` joakim
2015-02-01 16:30               ` Dmitry Gutov
2015-02-01 19:48                 ` joakim
2015-02-01 19:53                 ` Paul Eggert
2015-02-01 19:59                   ` joakim
2015-02-01 20:05                   ` Dmitry Gutov
2015-02-01 20:08             ` David Engster
2015-02-01 20:18               ` Dmitry Gutov
2015-02-01 20:21                 ` David Engster
2015-02-03 22:38         ` joakim
2015-02-03 23:42           ` Paul Eggert
2015-02-04 15:59             ` joakim
2015-02-04 18:57               ` joakim
2015-02-05  0:38                 ` Paul Eggert
2015-02-05 15:54                   ` joakim
2015-02-05 16:17                     ` Paul Eggert
2015-02-09 11:50                       ` joakim
2015-02-09 11:56                   ` joakim
2015-02-09 19:47                     ` Paul Eggert
2015-02-09 20:24                       ` joakim
2015-02-09 22:20                         ` Paul Eggert [this message]
2015-02-10 18:27                           ` joakim
2015-02-01 15:36     ` Eli Zaretskii
2015-02-01 15:51       ` David Engster
2015-02-01 15:52       ` joakim
2015-02-01 16:04         ` David Engster
2015-02-01 16:04         ` Eli Zaretskii
2015-02-01 16:05         ` Andreas Schwab
2015-02-01 16:11           ` David Engster
2015-02-01 16:15             ` Andreas Schwab
2015-02-01 16:18               ` joakim
2015-02-01 19:29               ` David Engster
2015-02-01 19:39                 ` Dmitry Gutov
2015-02-01 19:56                   ` Eli Zaretskii
2015-02-01 20:41                     ` Dmitry Gutov
2015-02-02  3:30                       ` Eli Zaretskii
2015-02-02  8:03                         ` David Engster
2015-02-02 10:53                           ` Ulrich Mueller
2015-02-02 16:30                           ` Eli Zaretskii
2015-02-02 23:19                             ` Stefan Monnier
2015-02-02  1:35                 ` Stephen J. Turnbull
2015-02-02  1:57                   ` Dmitry Gutov
2015-02-02  2:12                     ` Stephen J. Turnbull
2015-02-02  2:21                       ` Dmitry Gutov
2015-02-02  3:45                         ` Stephen J. Turnbull

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=54D932A9.1020004@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    /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.