Everyone -- thanks. Trying to respond to everyone without writing ten posts.
1. I understand the basic problem. There is no proc apparently that is C vs C++ independent. CBCC is indeed C++ specific. I *thought* I was using it to compile individual C programs and I was, sort of. They are C programs, but it is compiling them as C++ programs. 9 out of 10 C programs are of course valid C++ programs, and it was "working" fine. If you give it one .c file it compiles it as C++. If you give it a whole folder of .C and .c files it skips the .c files. Less than ideal but okay, I admit it, I didn't RTFM, at least not that chapter very carefully. Actually, it looks like just running CCNDRVR will do what I want, but some of my options are not valid for C programs, so maybe I don't really want to do what I think I want to do. 2. Yes, any language is obscure if you do not know it and makes perfect sense if you do. I am giving a presentation next week (anyone else going to Vanguard?) in which I will refer to some particular UNIX scripting as "incredibly geeky." And this to an audience of people who undoubtedly think JCL and RACF commands make all the sense in the world. 3. Yes, I should learn to use make. I admit it. I should also join a gym. I have not yet done either. 4. No need to eek, Gil. Yes, the compiler input and output is all in USS/HFS/zFS whatever. I may be stuck in JCL but I have grown beyond the eight-uppercase-character thing. 5. Yes, I find make $( ls *.[cC] | sed 's/\.[cC]$/.o/' ) to be scary. Actually, I can sort of parse it: list every file ending in .c or .C and pipe it into sed and then do something with it. 6. My use of JCL versus make has nothing to do with efficiency. I would assume they are equivalent in that regard. It has entirely to do with inertia. Been doin' compiles with JCL for nigh on forty years now. If JCL was good enough for me pappy it's good enough for me. JCL *is* a language for big room-sized computers with blinking lights. You got a problem with that? <g> Seriously, thanks everyone for your help. Especially Jack for RTFM for me. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jack J. Woehr Sent: Wednesday, September 23, 2015 10:45 AM To: [email protected] Subject: Re: Compiling a folder of mixed C and C++ John McKown wrote: > I don't know who came up with JCL (I was going to say "designed", but > decided that word just didn't fit) JCL is ...um ... cute. It looks like a language for the big, room-sized computers with the blinking lights used in 1950's sci-fi movies :) > Of course, for the BASH fans out there, BASH has some very "hairy" > things that can be done with it. Such as "process substitution". Tell me about it, I've written metalanguages more than once for autogenerating bash scripts. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
