From owner-freebsd-current  Thu Apr 10 23:13:13 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA28933
          for current-outgoing; Thu, 10 Apr 1997 23:13:13 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28925
          for <current@freebsd.org>; Thu, 10 Apr 1997 23:13:10 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA07220; Fri, 11 Apr 1997 16:08:39 +1000
Date: Fri, 11 Apr 1997 16:08:39 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199704110608.QAA07220@godzilla.zeta.org.au>
To: current@freebsd.org, jkh@time.cdrom.com
Subject: Re: Trivial Nit-Pick Of The Week.
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>/usr/include/malloc.h:2: warning: #warning "this file includes <malloc.h> which is obsoleted, use <stdlib.h> instead"
>
>Shouldn't cpp emit a more sensible:
>
>/usr/include/malloc.h:2: #warning "this file includes <malloc.h> which is obsoleted, use <stdlib.h> instead"
>
>It would be output more consistent with that of #error, for example.

It's actually already consistent, although not good.  All warnings are
prefixed by "warning: ", but there is no prefix for errors.  For both
#warning and #error, the full line is printed following the prefix.
Other braindamage: there is no prefix for "In function `foo':" or "At
top level:", so it is difficult to separate warnings from errors using
a simple regexp.

Fixing this might break complicated pattern matchers.

Bruce