All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
	Philip Oakley <philipoakley@iee.org>,
	Duy Nguyen <pclouds@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: /* compiler workaround */ - what was the issue?
Date: Fri, 06 May 2016 12:57:58 -0700	[thread overview]
Message-ID: <xmqqinyr2c3d.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <572CF0D5.6010305@xiplink.com> (Marc Branchaud's message of "Fri, 6 May 2016 15:30:29 -0400")

Marc Branchaud <marcnarc@xiplink.com> writes:

> On 2016-05-06 02:54 PM, Junio C Hamano wrote:
>>
>> I wonder if can we come up with a short and sweet notation to remind
>> futhre readers that this "initialization" is not initializing but
>> merely squelching warnings from stupid compilers, and agree to use
>> it consistently?
>
> Perhaps
>
> 	#define COMPILER_UNINITIALIZED_WARNING_INITIALIZER 0
>
> or, for short-and-sweet
>
> 	#define CUWI 0
>
> ?
>
> :)

I get that smiley.

I was hinting to keep the /* compiler workaround */ comment, but
in a bit shorter form.

  reply	other threads:[~2016-05-06 19:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AA5B2B1715BAF7438221293187A417A7BDE9D11D@desmdswms002.des.grplnk.net>
2016-05-05 20:48 ` /* compiler workaround */ - what was the issue? Philip Oakley
2016-05-05 21:41   ` Junio C Hamano
2016-05-06 10:17     ` Duy Nguyen
2016-05-06 13:15       ` Philip Oakley
2016-05-06 18:05         ` Ramsay Jones
2016-05-06 18:33           ` Philip Oakley
2016-05-06 18:54           ` Junio C Hamano
2016-05-06 19:30             ` Marc Branchaud
2016-05-06 19:57               ` Junio C Hamano [this message]
2016-05-06 20:01                 ` Stefan Beller
2016-05-09 19:40                   ` Philip Oakley
2016-05-09 19:49                     ` Randall S. Becker
2016-05-06 20:28                 ` Marc Branchaud
2016-05-06 20:21             ` Ramsay Jones
2016-05-06 21:17               ` Ramsay Jones

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=xmqqinyr2c3d.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=marcnarc@xiplink.com \
    --cc=pclouds@gmail.com \
    --cc=philipoakley@iee.org \
    --cc=ramsay@ramsayjones.plus.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. 
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.