From owner-freebsd-current  Fri Apr 11 12:05:38 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA12645
          for current-outgoing; Fri, 11 Apr 1997 12:05:38 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA12636
          for <current@freebsd.org>; Fri, 11 Apr 1997 12:05:32 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA11874; Fri, 11 Apr 1997 11:45:42 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199704111845.LAA11874@phaeton.artisoft.com>
Subject: Re: Trivial Nit-Pick Of The Week.
To: bde@zeta.org.au (Bruce Evans)
Date: Fri, 11 Apr 1997 11:45:42 -0700 (MST)
Cc: current@freebsd.org, jkh@time.cdrom.com
In-Reply-To: <199704110608.QAA07220@godzilla.zeta.org.au> from "Bruce Evans" at Apr 11, 97 04:08:39 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

[ ... #warning ... ]

> 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.

Where can I download one of these complicated pattern matchers?

8-).

Is there really code out there that depends on this behaviour?


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