From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d79d55198abf90d8 X-Google-Attributes: gid103376,public From: peter@nospam Subject: Re: Conditional Compilation Date: 2000/09/25 Message-ID: <8qnvpg02cgr@drn.newsguy.com>#1/1 X-Deja-AN: 673967772 References: <7FEFA9E5E3B3C4A5.90418F4BE7D5AE58.48E094CF81EC6BD3@lp.airnews.net> <8qauu3$7ei$1@nnrp1.deja.com> <8qlri4$gu2$1@nnrp1.deja.com> <39CEE3C5.42E8D8E5@telepath.com> Organization: - Newsgroups: comp.lang.ada Date: 2000-09-25T00:00:00+00:00 List-Id: In article <39CEE3C5.42E8D8E5@telepath.com>, Ted says... >A few hours of that is enough to convince anyone that >the man who forbade macros from Ada was a genius. > I saw once some C code where a comment before start of a function said: "Too large for a macro" Later I learned that the programmer did everything in macros, and only if they could not, resorted to functions. The most fun was when seeing a macro using other macros. (some C compiler would chock on this). Saw one C file which had 7 different compilation modes, and overlays between them. So complex, impossible to understand one mode from the other becuase every other line there is an #ifdef this_mode || that_mode, so the only way to understand the logic of each mode by itself, is to compile using -E flag (with one -Dmode_name) and then look at the outout of the pre-processor. one mode did not compile at all, it was missing header files. Later I learned this mode was no longer supported (so dead code sitting in there). One of the things I like about java (as with Ada) is lack of macros and pre-proccessor and everything that comes with that (i.e. the #define mess), and lack of header files. peter