From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai-git@xenomai.org, Jan Kiszka <jan.kiszka@siemens.com>,
xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : alchemy: Replace static variable no_alchemy_task with macro
Date: Tue, 04 Feb 2014 18:44:32 +0100 [thread overview]
Message-ID: <52F12700.3020400@xenomai.org> (raw)
In-Reply-To: <52F125E8.6020200@xenomai.org>
On 02/04/2014 06:39 PM, Philippe Gerum wrote:
> On 02/04/2014 06:32 PM, Gilles Chanteperdrix wrote:
>> On 02/04/2014 06:27 PM, Philippe Gerum wrote:
>>> If g++ chokes on the initializer part because it is outdated, then using
>>> old-fashioned ones may be an option. Actually, I find macroizing this
>>> definition quite bad.
>>>
>>> static const RT_TASK no_alchemy_task = {
>>> - .handle = 0,
>>> - .thread = 0
>>> + handle: 0,
>>> + thread: 0
>>> };
>>
>> No, the previous version is better, it is standard compliant C and C++,
>> the second version is a gcc extension, which works only when compiling
>> C, if I remember correctly.
>>
>
> Recent g++ is happy with both (no -std forced though). But the former is
> allowed by the C++ parser only since recently.
>
Well, on the other hand:
static const RT_TAKS no_alchemy_task;
Will zero initialized the structure just as well...
--
Gilles.
next prev parent reply other threads:[~2014-02-04 17:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WAhle-0006kB-0q@sd-51317.dedibox.fr>
2014-02-04 15:22 ` [Xenomai] [Xenomai-git] Jan Kiszka : alchemy: Replace static variable no_alchemy_task with macro Gilles Chanteperdrix
2014-02-04 16:36 ` Philippe Gerum
2014-02-04 17:12 ` Jan Kiszka
2014-02-04 17:27 ` Philippe Gerum
2014-02-04 17:32 ` Gilles Chanteperdrix
2014-02-04 17:35 ` Jan Kiszka
2014-02-04 17:39 ` Gilles Chanteperdrix
2014-02-04 17:39 ` Philippe Gerum
2014-02-04 17:44 ` Gilles Chanteperdrix [this message]
2014-02-04 17:46 ` Jan Kiszka
2014-02-04 17:48 ` Philippe Gerum
2014-02-04 17:53 ` Philippe Gerum
2014-02-04 18:03 ` Jan Kiszka
2014-02-04 18:20 ` Jan Kiszka
2014-02-04 18:26 ` Gilles Chanteperdrix
2014-02-04 18:35 ` Jan Kiszka
2014-02-05 9:07 ` Philippe Gerum
2014-02-05 8:33 ` Philippe Gerum
2014-02-05 8:49 ` Jan Kiszka
2014-02-05 8:58 ` Philippe Gerum
2014-02-05 9:06 ` Jan Kiszka
2014-02-05 9:36 ` Philippe Gerum
2014-02-05 9:42 ` Jan Kiszka
2014-02-05 10:10 ` Philippe Gerum
2014-02-05 10:28 ` Jan Kiszka
2014-02-06 15:24 ` Jan Kiszka
2014-02-05 7:30 ` dietmar.schindler
2014-02-04 17:31 ` Gilles Chanteperdrix
2014-02-04 17:35 ` Philippe Gerum
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=52F12700.3020400@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=rpm@xenomai.org \
--cc=xenomai-git@xenomai.org \
--cc=xenomai@xenomai.org \
/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.