On Sat, 2006-11-18 at 08:29 -0700, Jeffrey D. Smith wrote: > The shortage of good assembler programmers can be mitigated by hiring good > C programmers and using Systems/C as a development and educational tool. As > the C programmers become educated in mainframe assembler by looking at the > generated assembler, they can write assembler-only subroutines and easily > call those routines directly from their Systems/C programs. It's a great way > to "ease into" mainframe assembler programming from a higher level language.
I decided on a similar strategy when diving into Linux - grab the (kernel) source and teach myself. Problem was I didn't know either C *or* (x86) assembler. A barrel of laughs that was. Don't know whether Jeffreys suggestion would work in the real world or not. Depends on how good the compiler is I guess. Given the type of code he develops, this is a pretty good recommendation for Systems/C. > Also, a good set of debugging tools is vital for understanding the > difference between what you thought you wrote compared to what you > actually wrote. Go to www.colesoft.com for state of the art debugging > tools. I wish ... I can't get the people who hire me to lash out for Daves little beauty. The "test" command and IPCS are free. And yes, I *am* aware of the limitations. Shane ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
