From owner-freebsd-current  Sat Mar  1 16: 2:18 2003
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C60F037B401
	for <current@freebsd.org>; Sat,  1 Mar 2003 16:02:17 -0800 (PST)
Received: from mail.liwing.de (mail.liwing.de [213.70.188.162])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4A2C943FAF
	for <current@freebsd.org>; Sat,  1 Mar 2003 16:02:16 -0800 (PST)
	(envelope-from rehsack@liwing.de)
Received: (qmail 5448 invoked from network); 2 Mar 2003 00:02:15 -0000
Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164])
          (envelope-sender <rehsack@liwing.de>)
          by mail.liwing.de (qmail-ldap-1.03) with SMTP
          for <barney@pit.databus.com>; 2 Mar 2003 00:02:15 -0000
Message-ID: <3E614A06.5070403@liwing.de>
Date: Sun, 02 Mar 2003 01:02:14 +0100
From: Jens Rehsack <rehsack@liwing.de>
Organization: LiWing IT-Services
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Barney Wolff <barney@pit.databus.com>
Cc: current@freebsd.org, Juli Mallett <jmallett@FreeBSD.org>
Subject: Re: PATCH: type errors in src-tree
References: <3E5EA13E.9020208@liwing.de> <3E60F1CF.2030400@liwing.de> <20030301155546.A39174@FreeBSD.org> <3E612F7F.1090002@liwing.de> <20030301233642.GA64401@pit.databus.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Barney Wolff wrote:
> On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote:
> 
> Shouldn't we care about u_char vs char?  On some machines it matters,
> and on all machines compilers tend to notice and generate warnings.
> 

Just another question: I turned on '-ansi' and got some warning about a 
function declaration is not a prototype (all functions are declared in 
K&R style). Is it preferred by the FreeBSD-Team having functions in K&R 
styles or is the Ansi-Style on, too?

Jens


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message