On May 30 21:47, Ken Brown wrote:
> On 5/30/2016 8:14 PM, Ken Brown wrote:
> > On 5/30/2016 4:44 AM, Corinna Vinschen wrote:
> > > Our cdefs.h is taken almost verbatim from FreeBSD, and FreeBSD's
> > > cdefs.h uses the exact same expressions chcking for lint. I'm sure
> > > you'd see the same prob
On 5/30/2016 8:14 PM, Ken Brown wrote:
On 5/30/2016 4:44 AM, Corinna Vinschen wrote:
Our cdefs.h is taken almost verbatim from FreeBSD, and FreeBSD's
cdefs.h uses the exact same expressions chcking for lint. I'm sure
you'd see the same problems there. Don't set lint.
OK, emacs has now been c
On 5/30/2016 4:44 AM, Corinna Vinschen wrote:
Our cdefs.h is taken almost verbatim from FreeBSD, and FreeBSD's
cdefs.h uses the exact same expressions chcking for lint. I'm sure
you'd see the same problems there. Don't set lint.
OK, emacs has now been changed so that it no longer defines lint
Am 30.05.2016 um 10:44 schrieb Corinna Vinschen:
Our cdefs.h is taken almost verbatim from FreeBSD, and FreeBSD's
cdefs.h uses the exact same expressions chcking for lint.
That means almost nothing. The BSD guy might have a good,
platform-specific reason to assign a specific meaning to the m
On May 29 13:21, Ken Brown wrote:
> On 5/29/2016 12:56 PM, Andy Moreton wrote:
> > On Sun 29 May 2016, Ken Brown wrote:
> >
> > > If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a
> > > macro
> > > that expands to nothing. Is this intentional?
> > >
> > > Simple test case
On 5/29/2016 3:09 PM, Andy Moreton wrote:
On Sun 29 May 2016, Ken Brown wrote:
On 5/29/2016 12:56 PM, Andy Moreton wrote:
On Sun 29 May 2016, Ken Brown wrote:
If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a macro
that expands to nothing. Is this intentional?
Simple
On Sun 29 May 2016, Ken Brown wrote:
> On 5/29/2016 12:56 PM, Andy Moreton wrote:
>> On Sun 29 May 2016, Ken Brown wrote:
>>
>>> If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a
>>> macro
>>> that expands to nothing. Is this intentional?
>>>
>>> Simple test case:
>>>
>>>
On 5/29/2016 1:21 PM, Ken Brown wrote:
On 5/29/2016 12:56 PM, Andy Moreton wrote:
On Sun 29 May 2016, Ken Brown wrote:
If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn
as a macro
that expands to nothing. Is this intentional?
Simple test case:
$ cat test.h
#define lint 1
#
On 5/29/2016 12:56 PM, Andy Moreton wrote:
On Sun 29 May 2016, Ken Brown wrote:
If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a macro
that expands to nothing. Is this intentional?
Simple test case:
$ cat test.h
#define lint 1
#include
_Noreturn void foo (void);
$ g
On Sun 29 May 2016, Ken Brown wrote:
> If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a macro
> that expands to nothing. Is this intentional?
>
> Simple test case:
>
> $ cat test.h
> #define lint 1
> #include
> _Noreturn void foo (void);
>
> $ gcc -E test.h | grep foo
>
On 5/29/2016 9:42 AM, Ken Brown wrote:
> If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a
> macro that expands to nothing. Is this intentional?
>
> Simple test case:
>
> $ cat test.h
> #define lint 1
> #include
> _Noreturn void foo (void);
>
> $ gcc -E test.h | grep foo
If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a
macro that expands to nothing. Is this intentional?
Simple test case:
$ cat test.h
#define lint 1
#include
_Noreturn void foo (void);
$ gcc -E test.h | grep foo
void foo (void);
Ken
--
Problem reports:
12 matches
Mail list logo
