From owner-freebsd-hackers  Mon Aug 28 11:58:15 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA20358
          for hackers-outgoing; Mon, 28 Aug 1995 11:58:15 -0700
Received: from localhost (localhost [127.0.0.1])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id LAA20343
          ; Mon, 28 Aug 1995 11:58:12 -0700
Message-Id: <199508281858.LAA20343@freefall.FreeBSD.org>
X-Authentication-Warning: freefall.FreeBSD.org: Host localhost didn't use HELO protocol
To: Bruce Evans <bde@zeta.org.au>
cc: hackers@freefall.FreeBSD.org
Subject: Re: 16, 32, and 64bit types? 
In-reply-to: Your message of "Tue, 29 Aug 95 04:50:56 +1000."
             <199508281850.EAA10488@godzilla.zeta.org.au> 
Date: Mon, 28 Aug 1995 11:58:11 -0700
From: "Justin T. Gibbs" <gibbs@freefall.FreeBSD.org>
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>>that will always be 32bits.  NetBSD has u_int32 and 
>>friends for this type of task.  Do we have anything
>>similar?  If not, I think we should.  What would it
>>take to bring in the extra types?
>
>We have u_int32_t etc. in <sys/types.h> (actually in
><machine/types.h>.  u_int32 would pollute the namespace.
>
>Bruce

Yes, I meant u_int32_t.  Any reason sys/types.h doesn't use them
to express the other types?  This is how it is done in NetBSD.
--
Justin T. Gibbs
===========================================
  Software Developer - Walnut Creek CDROM
  FreeBSD: Turning PCs into workstations
===========================================