The problem getting addressed by Metal C is the capability of doing things in C that do not require the LE anchor to be used. And the dual source is not a problem when many of our C routines are already multi-compiled. We just use #ifdef/#ifndef with the appropriate system flags to bypass code not used in certain environments. In addition, you can use dataspaces and cross memory in Metal C that you cannot in "normal" C. Lloyd
>________________________________ > From: Paul Gilmartin <[email protected]> >To: [email protected] >Sent: Tuesday, March 25, 2014 7:24 PM >Subject: Re: Metal C vs. HLASM - for C callable subroutine? > >On Tue, 25 Mar 2014 19:15:45 -0400, Tony Harminc wrote: > >What business problem is IBM addressing with Metal C, anyway? >The solution to such a problem would be enhanced by easier >access to system facilities. The costs and risks of parallel source >maintenance are obvious. > >-- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
