Re: EBCDIC Bad History (was: Json table characters)

2018-08-10 Thread Paul Gilmartin
On Fri, 10 Aug 2018 16:38:26 -0400, Thomas David Rivers wrote: >> >#pragma codepage presents its on set of problems. > >Consider, for instance, you move the source into a Git repository >on a remote (and ASCII) system. And, if you have a cross-compiler, >might consider compiling on that remote sy

Re: EBCDIC Bad History (was: Json table characters)

2018-08-10 Thread Thomas David Rivers
David Crayford wrote: On 10/08/2018 7:34 PM, Peter Relson wrote: I have no idea why the health checker header files in SYS1.SIEAHDR.H(HZS*) chose to use them. Because no one was willing to take a stand that everyone has a system like yours that can handle the braces, at the expense of some

Re: EBCDIC Bad History (was: Json table characters)

2018-08-10 Thread David Crayford
On 10/08/2018 7:34 PM, Peter Relson wrote: I have no idea why the health checker header files in SYS1.SIEAHDR.H(HZS*) chose to use them. Because no one was willing to take a stand that everyone has a system like yours that can handle the braces, at the expense of someone who did not. You make

Re: EBCDIC Bad History (was: Json table characters)

2018-08-10 Thread Peter Relson
>I have no idea why the health checker header files in >SYS1.SIEAHDR.H(HZS*) chose to use them. Because no one was willing to take a stand that everyone has a system like yours that can handle the braces, at the expense of someone who did not. Nevertheless, it seems unlikely that there will be