<div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 9, 2019 at 11:21 PM Tom Honermann <<a href="mailto:tom@honermann.net">tom@honermann.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"><p>The constraint I'd most like feedback on is 1.1 (The ordinary and
wide execution encodings are implementation defined). If
Microsoft were to support use of UTF-8 as the execution encoding
(something they are making steps towards), it may be conceivable
that we could standardize the execution encoding as UTF-8 and have
that actually reflect existing practice (implementations would
presumably continue to offer support for legacy encodings as an
extension). However, this would leave some platforms behind; z/OS
being the primary example. z/OS continues to maintain a
significant presence in the industry (as I understand it, good
numbers are hard to find), but IBM has not been keeping up with
C++ standards. Some guidance regarding how to think about
platforms that are not keeping up with the standard would be
appreciated.<br></p></div></blockquote><div>IBM offers C++11 compilers compiling EBCDIC applications from EBCDIC source on z/OS. IBM also produces offerings of applications based on LLVM on z/OS, which would necessitate advances in the C++ support on the platform. Note that one of the advantages C++ has on z/OS over Java is that it is capable of communicating with the EBCDIC-based libraries and system services without a translation layer. If "C++ leaves no room for another language between itself and the hardware", then C++ for z/OS would have EBCDIC execution character sets.<br></div></div></div></div>