Sujet : Re: RP2350 and Pico 2 - things missing
De : steveo (at) *nospam* eircom.net (Ahem A Rivet's Shot)
Groupes : comp.sys.raspberry-piDate : 01. Sep 2024, 11:53:14
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240901115314.3d7795351c717fa546c0f6dc@eircom.net>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
User-Agent : Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0)
On Sun, 1 Sep 2024 11:07:17 +0100
mm0fmf <
none@invalid.com> wrote:
On 01/09/2024 08:50, Lawrence D'Oliveiro wrote:
On Thu, 29 Aug 2024 21:33:28 +0100, druck wrote:
Yes stdint.h is your friend
Unless you have an elderly code base that still hasn’t caught up with
C99 ...
Or you were programming in C on an Analog Devices SHARC were char was 32
bits.
I'll bet that broke a lot of bad code :)
Stll even in that environment a compliant compiler should still
provide int<n>_t types. They'd probably have to have horrendously
inefficient implementations not dissimilar to the bitfields in structs but
they should exist. Woe betide anyone who thought they could put a char into
an int16_t safely though.
-- Steve O'Hara-SmithOdds and Ends at http://www.sohara.org/For forms of government let fools contestWhate're is best administered is best - Alexander Pope