From owner-freebsd-current  Sun Mar 12 16:18:23 2000
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id F37A837B50E
	for <current@FreeBSD.ORG>; Sun, 12 Mar 2000 16:18:18 -0800 (PST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id TAA32652;
	Sun, 12 Mar 2000 19:18:16 -0500 (EST)
	(envelope-from wollman)
Date: Sun, 12 Mar 2000 19:18:16 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200003130018.TAA32652@khavrinen.lcs.mit.edu>
To: Paul Richards <paul@originative.co.uk>
Cc: keramida@ceid.upatras.gr, John Polstra <jdp@polstra.com>,
	current@FreeBSD.ORG
Subject: Re: MAX_UID ?
In-Reply-To: <38CC30FB.FC417909@originative.co.uk>
References: <38CAD957.3C839375@originative.co.uk>
	<200003120430.UAA49807@vashon.polstra.com>
	<38CB322D.D12ED0B0@originative.co.uk>
	<20000313015009.A5653@hades.hell.gr>
	<38CC30FB.FC417909@originative.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Mon, 13 Mar 2000 00:06:19 +0000, Paul Richards <paul@originative.co.uk> said:

> We could create a new include file that we use for constants that are
> related to FreeBSD specific types or we can agree on a coding style for
> performing bounds checking using tricks like ((uid_t)0-1)

Or we can do it the right way, by assigning to a variable of the
correct type and checking that the value remains unchanged.

-GAWollman


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