Re: RP2350 and Pico 2 - things missing

Ahem A Rivet's Shot <steveo@eircom.net> writes:

Richard Kettlewell <invalid@invalid.invalid> wrote:

I don’t think I’d fault either decision though the fact that we’ve
ended up with two conventions does make writing/maintaining portable
code a bit more annoying, though not really any more so than the slightly
different set of things compilers warn about or the lack of GCC
compatibility from MSVC. I think MS should bow the inevitable and
replace cl with Clang.

>
Portable code should only rely on the standards not implementations,
some very weird possibilities are legal within the standard.
>
There are always the int<n>_t types for when size matters.

Life is not always that simple and declaring how things ‘should’ be does
not fix a single line of code.

One of the public APIs we support largely uses ‘long’ and ‘unsigned
long’ for integral values, which causes occasional issues with our
cross-platform code. For example ‘unsigned long’ has the same size as
‘size_t’ on Linux, but not on 64-bit Windows.

--
https://www.greenend.org.uk/rjk/