Deutsch English Français Italiano |
<87zfog1w8f.fsf@nosuchdomain.example.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson <Keith.S.Thompson+u@gmail.com> Newsgroups: comp.lang.c Subject: Re: Top 10 most common hard skills listed on resumes... Date: Mon, 09 Sep 2024 12:08:00 -0700 Organization: None to speak of Lines: 30 Message-ID: <87zfog1w8f.fsf@nosuchdomain.example.com> References: <vab101$3er$1@reader1.panix.com> <vbcs65$eabn$1@dont-email.me> <vbekut$1kd24$1@paganini.bofh.team> <vbepcb$q6p2$1@dont-email.me> <vbgb5q$1ruv8$1@paganini.bofh.team> <vbhbbb$1blt4$1@dont-email.me> <vbipp5$24kl5$1@paganini.bofh.team> <vbk0d9$1tajm$1@dont-email.me> <vbkpfc$27l2o$1@paganini.bofh.team> <vbl3am$228vv$1@dont-email.me> <vblfgb$2dkij$1@paganini.bofh.team> <vblhp7$249ug$1@dont-email.me> <vbloje$2e34o$1@paganini.bofh.team> <vbmeae$2bn2v$2@dont-email.me> <vbn8pe$2g9i6$2@paganini.bofh.team> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Mon, 09 Sep 2024 21:08:01 +0200 (CEST) Injection-Info: dont-email.me; posting-host="5130c977fa34ae7ba7f2b29594baf74a"; logging-data="2647568"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/RnaqqHl709G97XIVsfW3a" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:X4j04Ke39dD7YWlBjQo/vxfF8XE= sha1:AQ0/fMemlJ28C+5N5uSv0dKfUSI= Bytes: 2779 Waldek Hebisch <antispam@fricas.org> writes: [...] > Concerning '<stdint.h>', somewhat worring thing is that several types > there seem to be optional (or maybe where optional in older versions > of the standard). I am not sure if this can be real problem, > but too many times I saw that on various issues developers say > "this in not mandatory, so we will skip it". I don't think you need to worry about it. The exact-width types are optional because some implementations might not be able to support them. For example, I've used systems that only had 8-bit and 64-bit integers; if the implementation I used had supported C99, it wouldn't have defined [u]int{16,32}_t. The exact-width types are not allowed to have padding bits, and the signed types must be 2's-complement (which C23 mandates for all signed integer types). But the vast majority of current systems support signed and unsigned types of 8, 16, 32, and 64 bits, and will support all 8 exact-width types. (And you can use, for example, `#ifdef UINT32_MAX` to test whether uint32_t is supported.) And it's likely that the "least" or "fast" types will be more suitable for your purpose. Those types are mandatory for widths of 8, 16, 32, and 64 bits. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com void Void(void) { Void(); } /* The recursive call of the void */