public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: sotrdg sotrdg via Libc-alpha <libc-alpha@sourceware.org>
Cc: sotrdg sotrdg <euloanty@live.com>
Subject: Re: A question about EBCDIC compiler
Date: Mon, 14 Sep 2020 10:54:59 +0200	[thread overview]
Message-ID: <87imcg7n6k.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CH2PR02MB6522603A0A9868E3644C4142B2230@CH2PR02MB6522.namprd02.prod.outlook.com> (sotrdg sotrdg via Libc-alpha's message of "Mon, 14 Sep 2020 04:36:25 +0000")

* sotrdg sotrdg via Libc-alpha:

> How does the compiler deal with characters with EBCDIC string
> literals enabled?
>
> How does glibc deal with EBCDIC compiler?

glibc has not been ported to any EBCDIC target, and I doubt it ever
will be ported to an operating systems that's primarily EBCDIC-based.

> For example
>
> printf(“Hello World: %d\n”,4);
>
> What encoding would this be on EBCDIC compiler? Will 4 become
> EBCDIC’s “4” or ASCII’s “4”?

The implementation is expected to output the character '4' for the
number.  The mechanism used for that is not specified.

In practice, I expect it will eventually converted to ASCII or UTF-8
these days because native EBCDIC terminals are extinct.  But on an
EBCDIC system, the program itself will write EBCDIC, it just gets
translated later.

> How does the filename get dealt with on EBCDIC compilers?

That depends a lot on on the operating system and the file system.
That's not really specific to EBCDIC, it's a fairly complex topic
everywhere (even on Linux, despite its generially lenient pathname
syntax).

  reply	other threads:[~2020-09-14  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  4:36 sotrdg sotrdg
2020-09-14  8:54 ` Florian Weimer [this message]
2020-09-15 19:46 ` Martin Sebor
2020-09-15 22:00   ` Joseph Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imcg7n6k.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=euloanty@live.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).