On Tue, 2022-03-22 at 14:32 +0000, Farley, Peter x23353 wrote: > +1 for MetalC. Puts it all under your control.
Why Metal/C? Metal/C is great for what it's designed for, which is systems level programming such as supervisor state, AR mode stuff etc. But it only has a tiny runtime library. If you wanted to do network programming using TCP sockets you would have to write your own code using the z/OS UNIX assembler callable services, and that's not much fun. Same for file I/O such as VSAM. I would much rather use C++ which has an extensive runtime library and lots of open source stuff I can download from Github. The REXX command processors I have written require LE for regular expressions or to use the Redis client libraries. I can't think of anything exciting that I could write in Metal/C. We're big Metal/C users but I wouldn't advocate it for anything other than as a high level assembler replacement with a superb optimizer. > > +10 for SAMPLIB members in MetalC, not that any such are very likely to be > provided in what's left of our working lifetimes. > > Peter > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Paul Gilmartin > Sent: Tuesday, March 22, 2022 9:31 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: looking for 'how to' developing Rexx host command > > EXTERNAL EMAIL > > On Mon, 21 Mar 2022 11:35:51 +0800, David Crayford wrote: > > > Wouldn't a SAMPLIB member be nice? In a HLL? > > > > Writing a REXX command processor in a HLL is non-trivial to do correctly. > > I've done it a few times and it requires creating a persistent LE > > environment ... > > > Well, then, Metal-C? > > RFE for SAMPLIB members? > > -- > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended > recipient or an authorized representative of the intended recipient, you are > hereby notified that any dissemination of this communication is strictly > prohibited. If you have received this > communication in error, please notify us immediately by e-mail and delete the > message and any attachments from your system. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
