From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-git@xenomai.org, xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : alchemy: Replace static variable no_alchemy_task with macro
Date: Wed, 05 Feb 2014 10:07:47 +0100 [thread overview]
Message-ID: <52F1FF63.9060103@xenomai.org> (raw)
In-Reply-To: <52F132D8.5000001@siemens.com>
On 02/04/2014 07:35 PM, Jan Kiszka wrote:
> On 2014-02-04 19:26, Gilles Chanteperdrix wrote:
>> On 02/04/2014 07:20 PM, Jan Kiszka wrote:
>>> On 2014-02-04 19:03, Jan Kiszka wrote:
>>>> BTW, there are way more issues with C++ when enabling standard
>>>> compliance. Not sure where all the errors come from and if they easy to
>>>> fixing. But I think we should try to be as clean as possible in out
>>>> external interfaces.
>>>
>>> GCC-only typeof is our problem. Simply doing
>>
>> What about __typeof__ ?
>
> Works fine, will queue a patch.
>
> Still, why do we have typeof in the cited cases? We know that the
> parameters are types and not variables, no?
>
COBALT_DECL(int (*)(void), foo(int arg)) will do the right thing with
typeof, but won't with a trivial preprocessor token substitution.
--
Philippe.
next prev parent reply other threads:[~2014-02-05 9:07 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
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 [this message]
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=52F1FF63.9060103@xenomai.org \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--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.