Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: VMS
Date: 27 Jun 2025 17:40:02 GMT
Lines: 11
Message-ID: <mc83bhFcp3sU1@mid.individual.net>
References: <wCqdnYde9MIbmND1nZ2dnZfqnPadnZ2d@giganews.com>
	<87tt4i9nw5.fsf@eder.anydns.info> <102l0h9$fjtb$5@dont-email.me>
	<Z2udned3u9ZgqtP1nZ2dnZfqnPudnZ2d@giganews.com>
	<slrn1054j9c.3ce8.candycanearter07@candydeb.host.invalid>
	<PpudnVnCnvuYxc_1nZ2dnZfqnPudnZ2d@giganews.com>
	<wwva564xjps.fsf@LkoBDZeT.terraraq.uk>
	<4_GdncCsf-Nqe8n1nZ2dnZfqnPSdnZ2d@giganews.com>
	<wwv5xgqkfl9.fsf@LkoBDZeT.terraraq.uk> <103392c$lpbg$5@dont-email.me>
	<1033o4a$1qj6$3@dont-email.me> <1033tv1$3aqu$3@dont-email.me>
	<1034pj8$a74s$1@dont-email.me> <mbmm2nFdsgcU2@mid.individual.net>
	<slrn105cajs.4vj.spamtrap42@one.localnet>
	<slrn105g20l.3q8n7.candycanearter07@candydeb.host.invalid>
	<slrn105k75h.h13.spamtrap42@one.localnet>
	<slrn105sci1.1ibsg.candycanearter07@candydeb.host.invalid>
	<wwv4iw1bpor.fsf@LkoBDZeT.terraraq.uk>
	<fPmcnaKaU81_TsP1nZ2dnZfqn_adnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net Z4yD5OhBK6FD+bCLB8P4kwBRxDmU1yq5n4eq2k8PPD2oz5KOZk
Cancel-Lock: sha1:tTuHw/Y9VE+lpjB561l8ETzcquk= sha256:kADnSz3VxKROSUAIY4cvTTRz2EGTbB1I1yngllQcYiU=
User-Agent: Pan/0.160 (Toresk; )

On Fri, 27 Jun 2025 13:24:06 -0400, c186282 wrote:

>   Some of us are old enough to remember when CPUs were
>    not always 4/8/16/32/64 ... plus even now they've added a lot of new
>    types like 128-bit ints. Simply ASSUMING an int is 16 bits is
>    'usually safe' but not necessarily 'best practice' and limits future
>    (or past) compatibility. 'C' lets you fly free ...
>    but that CAN be straight into a window pane

Assuming an int is 16 bits is not a good idea. I wouldn't even assume a 
short is 16 bits