Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: Beginner....Decimal/Octal converter help Date: Sun, 11 Sep 2022 06:57:48 -0700 Organization: A noiseless patient Spider Lines: 15 Message-ID: <864jxeqahv.fsf@linuxsc.com> References: <8ffd982c-2e82-4caa-9256-ec17be2efe56n@googlegroups.com> <86leqsr091.fsf@linuxsc.com> <875yhv30nu.fsf@bsb.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader01.eternal-september.org; posting-host="eacead3a04a98f103c487ee10dc191dc"; logging-data="2034517"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1964SeUVxxaW5yDGDzocACnfKB2Oxc0ICM=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:CtT5m+ZgMDGyNi0ZFkZfvFmsbso= sha1:MAOJuhAf9B/dTBMByZolN0m0Lsw= Xref: csiph.com comp.lang.c:167602 Ben Bacarisse writes: > Mind you, since char is guaranteed to be at least 8 bits wide, > unsigned char is effectively uint_least8_t. Note that these two types might not be the same type. The C standard allows the possibility that uint_least8_t might be an extended integer type, distinct from the standard integer type unisigned char. This distinction matters both because of pointer compatibility and because the standard character types get special treatment under the anti-aliasing rules. AFAICT there is never any reason to use uint_least8_t, except in those rare cases when uint_least8_t is used by virtue of needing to call a third-party library (and in that case it is likely that a poor choice was made by developers of that library).