From owner-freebsd-hackers Mon Jan 4 15:11:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20221 for freebsd-hackers-outgoing; Mon, 4 Jan 1999 15:11:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20216 for ; Mon, 4 Jan 1999 15:11:26 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id PAA24603; Mon, 4 Jan 1999 15:10:36 -0800 (PST) Date: Mon, 4 Jan 1999 15:10:36 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199901042310.PAA24603@math.berkeley.edu> To: grog@lemis.com Subject: Re: Finding unused functions Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's occurred to me that after rewriting some code, I have some unused > functions in a program. Are there any good automatic ways to find out > what they are, something like the warnings you get from cc about > unused variables? lint dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message