Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c++
Subject: Re: uint32_t is not the same as long unsigned int ?
Date: Fri, 03 Jan 2020 23:56:49 -0800
Organization: None to speak of
Lines: 20
Message-ID: <87k167odry.fsf@nosuchdomain.example.com>
References: <qup223$eje$1@dont-email.me> <qup3ng$krp$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="ae6c07825fe602dea7ed53b20475ec70"; logging-data="5503"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+P2TirFS69+my9X41tFNRE"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Cancel-Lock: sha1:Al9AVwA5xNMp7CLM+iO/86aGnLQ= sha1:VXACkTC3MVv/mIYpWsuJoJ7e4E0=
Xref: csiph.com comp.lang.c++:71086

James Kuyper <jameskuyper@alumni.caltech.edu> writes:
[...]
> The actual requirements are in terms of the required range of values
> that each standard integer type must be able to represent, and are
> incorporated by reference from the C standard. I've converted those
> ranges into bit counts to better match your question.

A quibble: the required ranges of values for the standard integer types
are copied from the C standard, but are not incorporated by reference.

> One a 64-bit machine, long is often a 64-bit type, with int being a 32
> bit type.

True, but Microsoft's compiler has 32-bit long even on 64-bit machines.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    [Note updated email address]
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */