Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Book on Microsoft C
Message-ID: <9937@smoke.BRL.MIL>
Date: 28 Mar 89 17:10:07 GMT
References: <754@oravax.UUCP> <225800146@uxe.cso.uiuc.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <225800146@uxe.cso.uiuc.edu> mcdonald@uxe.cso.uiuc.edu writes:
>"Portability" is a word seldom heard outside the academic discussions
>of Usenet.

That's utter nonsense.  Anyone concerned with getting his applications
to work on a wide variety of unlike systems quickly learns to care
about program and environment portability.  That doesn't necessarily
mean that code is ported with 0 adaptation, but rather that the changes
needed are designed to be minimal and cleanly isolated from the bulk of
the application.

There are numerous commercial software vendors who rely on portable C
programming practice as the basis for providing versions of their
products on as many popular machines as possible.