Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: RP2350 and Pico 2 - things missing
Date: Thu, 29 Aug 2024 13:09:36 +0100
Organization: A little, after lunch
Lines: 35
Message-ID: <vapoe0$3v5v2$2@dont-email.me>
References: <v9lbfn$10qjj$2@dont-email.me> <v9pj3v$1qse0$7@dont-email.me>
 <lin8sjFbh5vU1@mid.individual.net> <va6s6f$c7dr$1@dont-email.me>
 <50ae75b3cdb83be61d995844169642d211670e3e.camel@munted.eu>
 <20240822115703.a377f409dd25c1b1f76f6c61@eircom.net>
 <va9k44$s0gf$2@dont-email.me>
 <20240823111241.fa25c2e204942a50ef8ccac5@eircom.net>
 <vac28j$1ab6s$6@dont-email.me>
 <20240824091356.eadff502925e2f0760693e89@eircom.net>
 <vagq3v$2a0g5$3@dont-email.me> <vai25u$2fn77$1@dont-email.me>
 <vajkr1$2rhoq$1@dont-email.me> <vajvlj$2shf7$1@dont-email.me>
 <valnib$35rt8$3@dont-email.me> <vao1af$3jojc$1@dont-email.me>
 <wwv4j73zq32.fsf@LkoBDZeT.terraraq.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 29 Aug 2024 14:09:36 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="87291f96f447ee78300091a1ce02ee12";
	logging-data="4167650"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19mZQcqj4UGHMfauZC1AxdujaRTjw95k+8="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:vL4O5BcditbROrS4nqBHjvb1CG4=
Content-Language: en-GB
In-Reply-To: <wwv4j73zq32.fsf@LkoBDZeT.terraraq.uk>
Bytes: 3052

On 29/08/2024 09:32, Richard Kettlewell wrote:
> druck <news@druck.org.uk> writes:
>> 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:-
> 
> (Almost everyone; Cray had 64-bit int.)
> 
>> int=32 bits, long=64 bits, long long=64 bits
> 
> THe Windows approach is well within what the C language spec allows, and
> simplified the adaptation of existing Windows application code to 64-bit
> platforms. The equivalent exercise in Linux needed attention to anything
> that made (sometimes invisible) assumptions about the definition of
> long.
> 
> 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.
> 
Most code that cares seems to use things like int_32 or long_64 where it 
matters and macro expand that on a per target hardware basis

-- 
Climate Change: Socialism wearing a lab coat.