From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <52F1FF63.9060103@xenomai.org> Date: Wed, 05 Feb 2014 10:07:47 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <52F1172B.2080500@xenomai.org> <52F11F94.9000309@siemens.com> <52F1231A.7080603@xenomai.org> <52F12442.3040301@xenomai.org> <52F125E8.6020200@xenomai.org> <52F12700.3020400@xenomai.org> <52F12800.1030500@xenomai.org> <52F12937.3050105@xenomai.org> <52F12B7A.4060408@siemens.com> <52F12F68.9040605@siemens.com> <52F130E6.6050504@xenomai.org> <52F132D8.5000001@siemens.com> In-Reply-To: <52F132D8.5000001@siemens.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : alchemy: Replace static variable no_alchemy_task with macro List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka , Gilles Chanteperdrix Cc: xenomai-git@xenomai.org, xenomai@xenomai.org 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.