From owner-freebsd-hackers Tue Apr 30 23:00:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA16470 for hackers-outgoing; Tue, 30 Apr 1996 23:00:23 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA16450 Tue, 30 Apr 1996 23:00:15 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA10304; Wed, 1 May 1996 15:52:34 +1000 Date: Wed, 1 May 1996 15:52:34 +1000 From: Bruce Evans Message-Id: <199605010552.PAA10304@godzilla.zeta.org.au> To: gpalmer@freebsd.org, hackers@freebsd.org Subject: Re: Warnings in LINT Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What is the ``correct'' way to silence these warnings: >../../gnu/isdn/iitel.c:1: warning: `_itelid' defined but not used >../../gnu/isdn/isdn_ioctl.h:1: warning: `_isdn_ioctl_id' defined but not used Convert all static Id strings to comments. There are only a few, mostly in isdn, because we normally don't use them. Use static type_t const object = ...; for apparently-unused static objects. I'm not sure how to handle apparently- unused static functions. >My initial thought is to hide them with a KERN_RCS ifdef (inspired by >libc), but is that the right thing to do? Any other ideas? A library macro conditioned to produce comments instead of static strings might be best if it existed :-). Bruce