Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #103318
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: The C Library Reference Guide |
| Date | 2017-02-06 10:53 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <o7a61j$6ou$1@jstuckle.eternal-september.org> (permalink) |
| References | <o79hm0$svn$1@dont-email.me> <589862a6.6370671@news.xs4all.nl> <65026461-822c-489d-bedc-3bae9787b895@googlegroups.com> |
On 2/6/2017 9:33 AM, supercat@casperkitty.com wrote: > On Monday, February 6, 2017 at 5:56:37 AM UTC-6, Richard Bos wrote: >> It's not quite reliable for C89, either: >> - It assumes (1.2.7, appendix) the character set is ASCII, which is very >> common but still not entirely universal, and in any case, not required >> by the Standard. > > How many C99 or C11 implementations are there in which character codes 0-127 > represent anything other than ASCII? I've used target systems which had > non-ASCII character sets, and it would be handy if there were a C syntax to > create string literals by feeding source text through a mapping table, but > I'd be genuinely surprised if there have been any full C99 or C11 > implementations using EBCDIC or any other source character set. > Every one which runs on IBM-compatible mainframes uses EBCDIC. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
The C Library Reference Guide MehdiAmini <atorrses@gmail.com> - 2017-02-06 13:35 +0330
Re: The C Library Reference Guide Barry Schwarz <schwarzb@dqel.com> - 2017-02-06 03:42 -0800
Re: The C Library Reference Guide raltbos@xs4all.nl (Richard Bos) - 2017-02-06 11:56 +0000
Re: The C Library Reference Guide supercat@casperkitty.com - 2017-02-06 06:33 -0800
Re: The C Library Reference Guide raltbos@xs4all.nl (Richard Bos) - 2017-02-06 15:17 +0000
Re: The C Library Reference Guide Jerry Stuckle <jstucklex@attglobal.net> - 2017-02-06 10:53 -0500
Re: The C Library Reference Guide supercat@casperkitty.com - 2017-02-06 08:32 -0800
Re: The C Library Reference Guide Jerry Stuckle <jstucklex@attglobal.net> - 2017-02-06 11:47 -0500
Re: The C Library Reference Guide Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-06 09:01 -0800
Re: The C Library Reference Guide Barry Schwarz <schwarzb@dqel.com> - 2017-02-06 11:26 -0800
Re: The C Library Reference Guide Robert Wessel <robertwessel2@yahoo.com> - 2017-02-06 16:26 -0600
Re: The C Library Reference Guide Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-02-06 17:01 +0000
Re: The C Library Reference Guide supercat@casperkitty.com - 2017-02-06 09:45 -0800
Re: The C Library Reference Guide Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-02-06 18:03 +0000
Re: The C Library Reference Guide supercat@casperkitty.com - 2017-02-06 10:45 -0800
Re: The C Library Reference Guide Tim Rentsch <txr@alumni.caltech.edu> - 2017-02-09 07:58 -0800
Re: The C Library Reference Guide raltbos@xs4all.nl (Richard Bos) - 2017-02-06 20:43 +0000
Re: The C Library Reference Guide supercat@casperkitty.com - 2017-02-06 13:22 -0800
Re: The C Library Reference Guide raltbos@xs4all.nl (Richard Bos) - 2017-02-06 22:17 +0000
Re: The C Library Reference Guide Noob <root@127.0.0.1> - 2017-02-06 16:15 +0100
Re: The C Library Reference Guide luser droog <luser.droog@gmail.com> - 2017-02-06 10:34 -0800
Re: The C Library Reference Guide Tim Rentsch <txr@alumni.caltech.edu> - 2017-02-08 22:14 -0800
Re: The C Library Reference Guide Keith Thompson <kst-u@mib.org> - 2017-02-09 09:32 -0800
csiph-web