From owner-freebsd-current  Wed Mar 27 12:00:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA22175
          for current-outgoing; Wed, 27 Mar 1996 12:00:42 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA22170
          for <freebsd-current@freebsd.org>; Wed, 27 Mar 1996 12:00:40 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01800; Wed, 27 Mar 1996 12:59:07 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199603271959.MAA01800@phaeton.artisoft.com>
Subject: Re: lint
To: bde@zeta.org.au (Bruce Evans)
Date: Wed, 27 Mar 1996 12:59:07 -0700 (MST)
Cc: freebsd-current@freebsd.org, j@uriah.heep.sax.de
In-Reply-To: <199603270555.QAA17578@godzilla.zeta.org.au> from "Bruce Evans" at Mar 27, 96 04:55:00 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >Ah.  Hmm, does lint grok exotic thing like ``__attribute(dead2)''
> >anyway?  Or, does it simply drop the expression in the parens for an
> >__attribute() statement?  Well, in the latter case, it must fake
> >gcc >= 2.5, if i'm not mistaken.
> 
> It doesn't understand them even with -g.  I think the author plans to
> fix this.  There has to be a way to tell lint that certain functions
> don't return, and __attribute__((__noreturn__)) is a good way.

Putting "/* NOTREACHED*/" after the function call is the traditional
lint method... assuming this is supposed to be an implementation of
a traditional lint, instead of some new thing.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.