Re: C needs to evolve

From	Keith Thompson <kst-u@mib.org>
Newsgroups	comp.lang.c
Subject	Re: C needs to evolve
Date	2017-12-02 20:42 -0800
Organization	None to speak of
Message-ID	<ln609owhgg.fsf@kst-u.example.com> (permalink)
References	(1 earlier) <ovu71v$p35$7@dont-email.me> <QjxUB.105781$W61.83338@fx08.am4> <9be489e6-8c1e-4d5a-83f8-35960e6b28e3@googlegroups.com> <lna7z0wvfw.fsf@kst-u.example.com> <0c5be846-814a-48b4-86c5-bfd46c992f2c@googlegroups.com>

Show all headers | View raw

Felipe Ferreira <felipefsdev@gmail.com> writes:
[...]
> On Saturday, December 2, 2017 at 8:40:15 PM UTC-3, Keith Thompson wrote:
>> How would that help?

(Referring to the idea of using the <stdint.h> types in the standard
library.)

> Portability and safety. It's a good practice to use the types defined
> in stdint.h. It's safer (you have the guarantee that a integer
> `int32_t` has 32 bits, a integer `int64_t` has 64 bits and so on) and
> makes easier to port (you get no surprises between two platforms using
> those types). Imo, they are nicer to see in the code (more readable,
> but that's just my opinion, thus subjective). I don't doubt one day we
> will have the entire standard using them, but it's unlikely it will be
> with C2X. And then, while you are using stdint to keep your code
> secure and portable, you still have to use the non conformant standard
> lib.

You snipped the part where I asked for specific examples of standard
library functions where types defined in <stdint.h> would work better
than the types currently used.  Do you have such examples?

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: C needs to evolve Chris Ahlstrom <OFeem1987@teleworm.us> - 2017-12-02 07:28 -0500
  Re: C needs to evolve bartc <bc@freeuk.com> - 2017-12-02 12:50 +0000
    Re: C needs to evolve Felipe Ferreira <felipefsdev@gmail.com> - 2017-12-02 06:26 -0800
      Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-12-02 08:31 -0800
      Re: C needs to evolve "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-12-02 17:36 +0100
      Re: C needs to evolve Keith Thompson <kst-u@mib.org> - 2017-12-02 15:40 -0800
        Re: C needs to evolve Felipe Ferreira <felipefsdev@gmail.com> - 2017-12-02 17:40 -0800
          Re: C needs to evolve Felipe Ferreira <felipefsdev@gmail.com> - 2017-12-02 17:46 -0800
            Re: C needs to evolve Ian Collins <ian-news@hotmail.com> - 2017-12-03 14:53 +1300
          Re: C needs to evolve Keith Thompson <kst-u@mib.org> - 2017-12-02 20:42 -0800
      Re: C needs to evolve Richard Damon <Richard@Damon-Family.org> - 2017-12-02 21:56 -0500
        Re: C needs to evolve David Brown <david.brown@hesbynett.no> - 2017-12-03 19:45 +0100
          Re: C needs to evolve Felipe Ferreira <felipefsdev@gmail.com> - 2017-12-03 11:35 -0800
            Re: C needs to evolve David Brown <david.brown@hesbynett.no> - 2017-12-03 21:58 +0100
            Re: C needs to evolve James Kuyper <jameskuyper@verizon.net> - 2017-12-03 21:01 -0500
            Re: C needs to evolve Keith Thompson <kst-u@mib.org> - 2017-12-03 23:02 -0800
          Re: C needs to evolve Thiago Adams <thiago.adams@gmail.com> - 2017-12-03 12:39 -0800
            Re: C needs to evolve David Brown <david.brown@hesbynett.no> - 2017-12-03 22:07 +0100
    Re: C needs to evolve Ian Collins <ian-news@hotmail.com> - 2017-12-03 11:34 +1300
    Re: C needs to evolve Melzzzzz <Melzzzzz@zzzzz.com> - 2017-12-03 05:25 +0000
      Re: C needs to evolve bartc <bc@freeuk.com> - 2017-12-03 12:37 +0000

csiph-web