If it has to compile under C then it's safer to test with a compiler that lag 
violations of C. If it only has to compile under C++, then why limit yourself 
to C syntax?

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר




________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Kirk Wolf <[email protected]>
Sent: Monday, September 7, 2026 1:41 PM
To: [email protected] <[email protected]>
Subject: Re: IBM and Arm Unveil Dual-Architecture Chip Plan for Future Z and 
LinuxONE Mainframes


External Message: Use Caution


This is a little off topic and probably controversial, but IMO it shouldn't be.

I argue that there is no longer many reasons to use a "C" compiler when you can 
use a "C++" compiler.  If you choose, you can only use a small number of the 
C++ features; a practice known as "Better C".   Note: writing OS kernel code is 
exception, but the reason isn't really performance.

What do you get?  Better type checking, better memory safety, better code 
readability.  Don't write classes if you don't want ( but I would, just could I 
could use RAII). Use "extern C" linkages if you like.   But you can use 
selective features like std::string, etc.  Writing pseudo string "classes" for 
C doesn't make sense to me in 202X.  Have a ton of C library code that you 
don't want to tweak to compile under C++?  You can mix and match C and C++ 
routines with the program binder - all you need to do is to update their 
headers that will be used from C++ to declare "C" linkage.

Kirk Wolf
Dovetailed Technologies
https://coztoolkit.com/

On Mon, Sep 7, 2026, at 5:09 AM, Clement Clarke wrote:
> I have been developing a few things over many years.  I wonder if they
> might be useful here?
>
> 1. I have a convertor that takes 370 instructions and converts them to
> X86. It can run under Borland's old IDE, so you can step through code,
> stop, go backwards,look at the simulated registers and so forth. It
> could be changed for ARM I suspect.
>
> 2. Just recently, I have updated some code that provides fast safe C
> strings. Works in C on Z series and C for Intel, so I suppose for ARM
> too.
>
> 3. Code to create RECFM=VB files in C with GCC and CLANG on Windows
> and Linux, so presumably where ever ARM is too.  These files are fully
> compatible with IBM VB files.  See
> http://www.github.com/Clemcl/fastsafestrings.
>
> 4. A simple PANEL instruction that works on Z/OS, Linux and Windows.
> The Z/OS version is in 370 assembler, and a C version is available for
> Windows and Linux.  For example:
>
>    PANEL ('Enter Your name:',name,30,'default')
>                ('Address;      ',address,50,'');
>
>    Popups and Menubars are supported.  See http://www.oscar-jol.com/ front
> page for an example.
>
> 5. Jol - the alternative to JCL.  A 370 ASsembler version and a C
> version that runs on Windows and Linux.
>
>     Jol is very similar to PL/I.
>
>      It can create highly optimised JCL, or run programs with Dynamic
> Allocation, in background or under TSO.
>
>      Jol has a macro language that makes it easy to create new
> instructions.  It has full Symbolic Variable processing.  It can
> allocate and create data sets in background or under TSO.  Or Windows.
>
>      It includes the PANEL instruction mentioned above.
>
>      Details are at http://www.oscar-jol.com/
>
> Clem Clarke
>
>
> On Sat, Sep 5, 2026 at 2:35 PM Mike Schwab
> <[email protected]> wrote:
> >
> > z/OS z/VM runs containers.
> > https://www.ibm.com/products/zos-container-platform
> > https://docs.redhat.com/en/documentation/openshift_container_platform/4.8/html/installing/installing-with-z-vm-on-ibm-z-and-linuxone
> >
> > On Fri, Sep 4, 2026 at 8:26 PM Andrew Rowley
> > <[email protected]> wrote:
> > >
> > > On 5/09/2026 5:42 am, Phil Smith III wrote:
> > > > If the idea for ARM on Z is to allow ARM binaries to run alongside Z 
> > > > binaries, how does that work with Big and Little Endian? Or will there 
> > > > be Middle Endian?*
> > > I'm not sure that big/little endian is a big deal. It affects the
> > > behavior of a few instructions, but you're running a different
> > > instruction set anyway. More interesting is the question of how the
> > > system knows whether this sequence of 1s and 0s is Z instructions or
> > > ARM. I guess it could work similarly to AMODE with an explicit switch.
> > >
> > > My question is why? Are there ARM programs out there that people want to
> > > run on Z but can't recompile? I doubt it. OS functions are usually the
> > > problem rather than the machine instructions.
> > >
> > > <speculation>
> > > IBM want to stop making specialized CPUs and switch to ARM processors.
> > > However there *is* a lot of z/OS software that can't be recompiled for
> > > another platform. Particularly assembler but other stuff as well. How
> > > might it work? Switch to ARM processors. Implement Z instructions in
> > > microcode. For maximum performance, recompile programs targeting ARM.
> > > Otherwise, z/OS instructions are handled by microcode (many probably map
> > > 1:1 to an ARM instruction). For systems running processors at less than
> > > full speed, it's probably not hard to tweak the dial to give the same
> > > performance as current systems...
> > > </speculation>
> > >
> > > --
> > > Andrew Rowley
> > > Black Hill Software
> > >
> > >
> > > ----------------------------------------------------------------------
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to [email protected] with the message: INFO IBM-MAIN
> >
> >
> >
> > --
> > Mike A Schwab, Springfield IL USA
> > Where do Forest Rangers go to get away from it all?
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to