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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,38159b1b5557a2e7 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-01-21 05:12:20 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!cs.tu-berlin.de!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: Standard Ada Preprocessor Date: Wed, 21 Jan 2004 13:12:19 +0000 (UTC) Organization: GMUGHDU Message-ID: References: <400A9B48.3060100@noplace.com> <400BD4B5.6000307@noplace.com> <400BDB7C.40100@noplace.com> <400D2150.6000705@noplace.com> <400E72F9.8060501@noplace.com> NNTP-Posting-Host: l1-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1074690739 9942 134.91.1.34 (21 Jan 2004 13:12:19 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Wed, 21 Jan 2004 13:12:19 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/800)) Xref: archiver1.google.com comp.lang.ada:4601 Date: 2004-01-21T13:12:19+00:00 List-Id: Marin David Condic wrote: : Even if you have the same target hardware and two different compilers : (even from the same manufacturer sometimes!) you can have statements : that will compile on one but not on the other. But then this is not an issue of program portability, but of compiler differences or compiler bugs. To some extent Source Code Versioning software and branches can help. : Isolation with separate : bodies is sometimes difficult to do and always complicates the build : process. Some form of conditional compilation would make the job easier. I'd prefer a conditional build process. IMHO, there should be a declarative language for build processes, integrated with one or more "source languages". ACE files (Eiffel), Project files (Ada), VCS integration/awareness etc. : Naturally that has risks and can lead to all sorts of abuse. If you keep the #ifs out of the code, and instead declare the target/compiler dependences in documents of their own right, to be processed by a configuration preprocessor, that risk isn't there, I think. -- Georg