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,13f10cac2d21b84f
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-05-02 08:26:08 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator2-SanJose!propagator-SanJose!in.nntp.be!news-in-sanjose!newsfeed.onecall.net!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.ada
Subject: Re: Is this a GNAT bug???
Date: 2 May 2002 10:25:58 -0500
Organization: LJK Software
Message-ID: <UfXoVGequmsV@eisner.encompasserve.org>
References: <db500a4f.0204300841.3f1f15a8@posting.google.com>
 <9gBz8.4053$451.2378814669@newssvr21.news.prodigy.com>
 <db500a4f.0204301731.391cd20a@posting.google.com>
 <4519e058.0205010908.7ebc64fd@posting.google.com>
 <D6MJOo3X5NAi@eisner.encompasserve.org> <3CD1475B.482F5E85@raytheon.com>
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 1020353161 17921 192.135.80.34 (2 May 2002
 15:26:01 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Thu, 2 May 2002 15:26:01 +0000 (UTC)
Xref: archiver1.google.com comp.lang.ada:23412
Date: 2002-05-02T10:25:58-05:00
List-Id: <comp.lang.ada>

In article <3CD1475B.482F5E85@raytheon.com>, Mark Johnson <mark_h_johnson@raytheon.com> writes:
> Larry Kilgallen wrote:
>> 
>> Portability in this regard is not so important if the rest of the
>> program is specific to a particular environment for other reasons.
> 
> Don't discount the need for portability. I have worked on at least two
> projects in the last 10 years where we moved code that was over 8-10
> years old between platforms. The first one replaced a system with 2 on
> site support engineers and < 100 hour MTBF with a system that had on
> call support and > 1700 hour MTBF. The second system has >$300k/year
> maintenance and the replacement hardware cost about $200k. Making it
> easy to do the move can be done without a significant cost today - if
> you use the right methods.

Ok, I will be specific.

Software to interact with a particular operating system, the only
purpose being support of that operating system.