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,f34f1a1939dc0c40 X-Google-Attributes: gid103376,public From: Laurent Guerby Subject: Re: conditional compilation Date: 2000/08/01 Message-ID: <8666pk6edg.fsf@acm.org>#1/1 X-Deja-AN: 653295794 References: <87d7jvp3qq.fsf@chiark.greenend.org.uk> <39857E5F.33C40014@acm.com> <3985FB16.82D140BB@below.for.email.address> <8m6log$r3a$1@nnrp1.deja.com> X-Trace: front3m.grolier.fr 965153435 6328 195.36.170.232 (1 Aug 2000 18:10:35 GMT) Organization: Club-Internet (France) NNTP-Posting-Date: 1 Aug 2000 18:10:35 GMT Newsgroups: comp.lang.ada Date: 2000-08-01T18:10:35+00:00 List-Id: Robert A Duff writes: > [...] So if you're going to use that approach, it's important to make the > target dependent files as small as possible -- make them contain *only* > the stuff that really needs to be target dependent. I do think this is pertinent to any method to manage target dependant code, ie make it nonexistant or as small as possible, and in addition write piles of documentation on the why side, mention it in the top level internal documentation. > Unfortunately, you might not know which code is target dependent > ahead of time. [...] I would say that it is true only when writing your first multi target software. After that, you get the idea ;-). -- Laurent Guerby