Re: RP2350 and Pico 2 - things missing

On 28/08/2024 21:29, druck wrote:

On 28/08/2024 00:30, Lawrence D'Oliveiro wrote:

On Tue, 27 Aug 2024 08:36:18 +0100, mm0fmf wrote:
>

On 27/08/2024 05:31, Lawrence D'Oliveiro wrote:

On Mon, 26 Aug 2024 15:06:52 +0100, mm0fmf wrote:

Win32 is the name of the API.

>
Why is it not “Win64”?

>
The 64bit version is the same API compiled for 64bit instead of 32bit.

>
That’s the trouble. It hasn’t really adapted to the availability as
standard of 64-bit integers, for example.
>
Compare the POSIX APIs, where they were careful to use generic types like
“size_t” and “time_t”, so that the same code could be compiled, unchanged,
to work on both 32-bit and 64-bit architectures. Not something Windows
code can manage.

 You can do this on Windows too, but they had to bastardise their C compiler for people that hadn't. It's the only one that on a 64 bit platform that has long as 32 bits.
 Windows:-
 int=32 bits, long=32 bits, long long=64 bits
 Everyone else in the bloody world:-
 int=32 bits, long=64 bits, long long=64 bits
 ---druck
 

The original PDP on which C was written had int 16 bits and long 32 bits
K & R specifically said that no size should be inferred for int. It was the length of a native word on the machines
--
"The great thing about Glasgow is that if there's a nuclear attack it'll look exactly the same afterwards."
Billy Connolly