On Thu, 18 Mar 2021, Thomas Klausner wrote:
with -S, one more warning is removed, but still a lot remain:
inttypes.h(66): warning: struct _locale never defined [233]
ansi.h(51): warning: struct __tag_wctrans_t never defined [233]
ansi.h(54): warning: struct __tag_wctype_t never defined [233]
On Thu, Mar 18, 2021 at 09:01:47AM +0100, Roland Illig wrote:
> Another thing is to check for GNU-specific C features such as
> __FUNCTION__ (which is easy to avoid in C99), ({...}), array
> initialization with [a...b], and so on. I don't think even GCC can
> reliably detect these.
Doesn't lint
On 17.03.2021 09:07, Valery Ushakov wrote:
On Wed, Mar 17, 2021 at 00:55:03 +0100, Roland Illig wrote:
Frankly, with modern compilers I don't see much (any, more like) point
of using lint on modern code. Playing catch up with gcc extensions
doesn't add much value compared to gcc/clang.
I
On 3/17/21 2:32 PM, Hauke Fath wrote:
OTOH, I guess I‘ve seen too many people trying to be productive by
removing features that _they_ don't need...
+1
That seems to be a "modern" way of contributing, without much need for
knowledge...
On Wed, 17 Mar 2021 00:55:03 +0100, Roland Illig wrote:
> when I run lint with the -t flag for traditional C (which means before
> C90), I always get these warnings:
>
> [...]
> Any objections to removing the -t flag and everything that belongs to it?
It seems to me the flag does what's
> On Mar 16, 2021, at 4:55 PM, Roland Illig wrote:
>
> Any objections to removing the -t flag and everything that belongs to it?
No objections from me.
-- thorpej
Hi,
when I run lint with the -t flag for traditional C (which means before
C90), I always get these warnings:
$ >empty.c
$ lint -t empty.c
(1): warning: 'long double' is illegal in traditional C [266]
(1): warning: function prototypes are illegal in traditional C [270]
(2): warning: 'long
