Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #108188

Re: Double-underline-itis

From Tim Rentsch <txr@alumni.caltech.edu>
Newsgroups comp.lang.c
Subject Re: Double-underline-itis
Date 2017-04-16 18:45 -0700
Organization A noiseless patient Spider
Message-ID <kfna87f958k.fsf@x-alumni2.alumni.caltech.edu> (permalink)
References (1 earlier) <87tw7doktz.fsf@bsb.me.uk> <o96c5h$l84$1@dont-email.me> <878topnpqm.fsf@bsb.me.uk> <o96gp9$d8n$1@dont-email.me> <lnd1e0dhw0.fsf@kst-u.example.com>

Show all headers | View raw


Keith Thompson <kst-u@mib.org> writes:

> BartC <bc@freeuk.com> writes:
> [...]
>> I've just come across __signed__!  How many C systems don't
>> support 'signed'?
>>
>>     typedef __signed__ char __s8;
>>     typedef unsigned char __u8;
>
> [...]
>
> The "signed" keyword and the signed char type were, IIRC, introduced
> by ANSI C in 1989.  A header designed to work with both pre-ANSI
> and ANSI C would have to have some way of dealing with that.  And
> since the header still works even with C11 (as long as __signed__
> is defined properly), there's not much motivation to fix it --
> unless you wrongly assume that headers are intended as end user
> documentation.
>
> The use of __s8 and __u8, rather than the standard int8_t and
> uint8_t, already implies that this is from an old legacy header.

It probably is from an old header, but using __s8 and __u8 (as
opposed to int8_t and uint8_t) doesn't necessarily imply that.
The __u8 and __s8 types, as typedef'ed above, are more widely
applicable than the [u]int8_t types, for a variety of reasons.
Presumably someone concerned with maximizing portability
would be aware of such concerns.

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


Thread

Double-underline-itis BartC <bc@freeuk.com> - 2017-02-28 23:44 +0000
  Re: Double-underline-itis supercat@casperkitty.com - 2017-02-28 15:54 -0800
  Re: Double-underline-itis Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-01 01:19 +0000
    Re: Double-underline-itis David Brown <david.brown@hesbynett.no> - 2017-03-01 09:11 +0100
    Re: Double-underline-itis BartC <bc@freeuk.com> - 2017-03-01 11:45 +0000
      Re: Double-underline-itis Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-01 12:30 +0000
        Re: Double-underline-itis BartC <bc@freeuk.com> - 2017-03-01 13:04 +0000
          Re: Double-underline-itis Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-01 15:29 +0000
            Re: Double-underline-itis gazelle@shell.xmission.com (Kenny McCormack) - 2017-03-01 15:47 +0000
          Re: Double-underline-itis Keith Thompson <kst-u@mib.org> - 2017-03-01 09:30 -0800
            Re: Double-underline-itis supercat@casperkitty.com - 2017-03-01 10:14 -0800
            Re: Double-underline-itis Tim Rentsch <txr@alumni.caltech.edu> - 2017-04-16 18:45 -0700

csiph-web