Re: lint libraries? (regarding common/lib/libc/hash/murmurhash/murmurhash.c(56): warning: constant in conditional context [161])

[Roland Illig <roland.illig%gmx.de@localhost>]

Am 05.04.2025 um 02:11 schrieb Greg A. Woods:
> I dunno how useful xlint libraries are as I've been more accustomed to
> the old Unix lint libraries (which are even useful standalone, see
> below), but perhaps if productive work is being on xlint, and it is
> gaining enough utility, then maybe it makes sense to turn on MKLINT=yes
> for at least the daily builds, possibly even for everyone?

I wonder how much longer the daily builds would take with MKLINT=yes.

Right now, the lint builds are done on 4 platforms, about once every 5
days, and Christos and me are looking regularly into the build results
to fix any fallout.

> Unix lint was basically hobbled to the point of being nearly useless for
> systems programming work without the system lint libraries being
> available (but then I think they were always supplied in my experience,
> and only deleted by non-programmer admins wanting to free up disk space
> that was so precious in the ancient days).

Was that in the pre-C90 days? Since then, functions have their
prototypes declared, which produces helpful compilation errors.

> typeof ()
> {
> 	...
> 	egrep -i "$1" $LLIBDIR/llib-l*
> }

What about:

man "$1"

grep "^$1" $(make -v .ALLTARGETS)

grep "[0-9]$1" /usr/libdata/lint/llib-*

Roland