All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] tools: use C99 __VA_ARGS__
Date: Tue, 21 Jul 2009 15:47:20 +0200	[thread overview]
Message-ID: <200907211547.20773.Christoph.Egger@amd.com> (raw)
In-Reply-To: <19045.49654.819861.134478@mariner.uk.xensource.com>

On Tuesday 21 July 2009 15:26:14 Ian Jackson wrote:
> Christoph Egger writes ("[Xen-devel] [PATCH] tools: use C99 __VA_ARGS__"):
> > Attached patch switches tools to consistently use C99 __VA_ARGS__.
>
> What is the benefit of this ?

Consistency in the whole tree in combination with two other patches
(xen-kernel and minios) which I have not yet submitted.

> Xen requires GCC and the GCC variable 
> argument list extension has been around forever,

That's not a reason to stick on old things.

> so it doesn't seem to aid portability.

No, not in this case.

But the other patch for the xen-kernel touches
the public headers.
AFAIK the public headers should follow the standard.

> The GCC syntax is considerably prettier than the C99 one.

This is subjective.

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2009-07-21 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 13:01 [PATCH] tools: use C99 __VA_ARGS__ Christoph Egger
2009-07-21 13:26 ` Ian Jackson
2009-07-21 13:47   ` Christoph Egger [this message]
2009-07-21 13:50     ` Ian Jackson
2009-07-21 14:26       ` Christoph Egger
2009-07-21 14:35         ` Keir Fraser
2009-07-21 14:24     ` Keir Fraser

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=200907211547.20773.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.