| Deutsch English Français Italiano |
|
<vapfp3$3sr5g$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Pancho <Pancho.Jones@proton.me> Newsgroups: comp.sys.raspberry-pi Subject: Re: RP2350 and Pico 2 - things missing Date: Thu, 29 Aug 2024 10:41:55 +0100 Organization: A noiseless patient Spider Lines: 27 Message-ID: <vapfp3$3sr5g$1@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> <20240829102839.5bb67af25e568ebabc65ede6@eircom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Thu, 29 Aug 2024 11:41:55 +0200 (CEST) Injection-Info: dont-email.me; posting-host="1c4e1d1e55d5a7317441d8bfc36f8a71"; logging-data="4091056"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+c3LJscXJPGqYC3qChq0r5mkkTDE7kWm4=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:lTvAsbbbMRprygxKScsLOjLiKLg= Content-Language: en-GB In-Reply-To: <20240829102839.5bb67af25e568ebabc65ede6@eircom.net> Bytes: 2676 On 29/08/2024 10:28, Ahem A Rivet's Shot wrote: > On Thu, 29 Aug 2024 09:32:49 +0100 > 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, > > 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. > Yes, from what I remember of the 90s, Microsoft code used typedefs, Int32, Int64 or maybe even Macros for types. Big projects sometimes used their own typedefs. I never liked it. I used int and long, but I recognised my code was suboptimal. Then I moved to Csharp and Java and stop worrying :-). C was shit, for not making types explicit, subsequent OS software developers were just polishing the turd.