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,355f90547d1b4b5
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: PRECOMPILATION
Date: 1999/02/28
Message-ID: <wccpv6ul7w2.fsf@world.std.com>#1/1
X-Deja-AN: 449580169
Sender: bobduff@world.std.com (Robert A Duff)
References: <918556681.260459@dedale.pandemonium.fr>
 <36C0B5D4.DEF83A66@averstar.com> <7ahor8$otv@news1.newsguy.com>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1999-02-28T00:00:00+00:00
List-Id: <comp.lang.ada>

Samuel Mize <smize@imagin.net> writes:

> C-experienced people probably expect platform-specific issues to be
> shot through the whole program, like cancer.  For instance, if a
> system call's parameter can be 64-bit or 32-bit depending on the
> platform, you may have #ifdefs around every call to it, and every
> declaration of a variable to use as a parameter for it.

Yeah, I've seen lots of code like that.  But it seems like a bad way to
do things, no matter *what* language you're using.

- Bob
-- 
Change robert to bob to get my real email address.  Sorry.