From owner-freebsd-hackers  Fri Nov 24 07:36:55 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id HAA25181
          for hackers-outgoing; Fri, 24 Nov 1995 07:36:55 -0800
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA25173
          for <hackers@freebsd.org>; Fri, 24 Nov 1995 07:36:50 -0800
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA10544
  (5.67a/IDA-1.5); Fri, 24 Nov 1995 09:30:46 -0600
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id JAA12572; Fri, 24 Nov 1995 09:10:07 -0600
Date: Fri, 24 Nov 1995 09:10:07 -0600
From: peter@taronga.com (Peter da Silva)
Message-Id: <199511241510.JAA12572@bonkers.taronga.com>
To: hackers@freebsd.org
Subject: How long is long?
	Re: SYSCALL IDEAS
	Was: cvs commit: src/sys/kern sysv_msg.c sysv_sem.c sysv_shm.c
Organization: Taronga Park BBS
Cc: terry@lambert.org
Sender: owner-hackers@freebsd.org
Precedence: bulk

Terry Lambert  <terry@lambert.org> wrote:
>That's a bug in the standard in not having mechanisms for obtaining
>sized types.  For a 64 bit int (requiring a 64 bit long), short is
                                             ^^-- 128
>either 16 or 32 bits (undefined) and we lose access to either 32 or
>16 bit types (respectively).

What architecture requires a 64 bit (int)?

IMHO, DEC did exactly the right thing making int 32 bits and long 64 bits,
given the history of the language, but IMHO the original BSD port to the
VAX should have done the same thing, rather than keeping it 32 bits for
easier porting of PDP-11 code.

Long doesn't and shouldn't mean "32 bits".