On Thursday, September 26, 2019, 12:31:23 PM PDT, Seymour J Metz <sme...@gmu.edu> wrote: > The definition of macro has never been the same as copy.
Seriously! The most sophisticated C macro possible is "#DEFINE MYMAC B C D ". Calling the macro "A MYMAC Y" results in "A B C D E". Additional macro substitution could occur for B, C or D if they exist. How is this anything more than copy? If you find a complicated C macro, please remove the C code before forwarding it. I may have overlooked something but I think it will result in the substitution logic described above. > Google for, e.g., #def, #if. I wish you could google. You would find that #IF cannot be used in a C macro (#DEFINE). C macro's only allow C code and C macro calls. #IF is in fact a preprocessor directive and are outside the scope of macro's. There are reason's that C macro's are strongly discouraged except in specific situations. > I don't know what you consider to be the "current" definition, > but the first hit that I got ha nothing to do with copy books., nor do macros > in C. I'm flexible. Use any definition for macro where C macro's meet the requirement. How do copy books not meet this definition? Jon. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
