Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!teknowledge-vaxc!sri-unix!garth!smryan
From: smryan@garth.UUCP (Steven Ryan)
Newsgroups: comp.lang.c
Subject: Re: Machines for testing portability (was Re: "Numerical Recipes in C" is nonportable code)
Message-ID: <1359@garth.UUCP>
Date: 1 Sep 88 20:21:52 GMT
References: <664@lindy.Stanford.EDU> <6758@megaron.arizona.edu> <718@gtx.com> <13258@mimsy.UUCP> <531@accelerator.eng.ohio-state.edu> <1673@dataio.Data-IO.COM> <673@proxftl.UUCP>
Reply-To: smryan@garth.UUCP (Steven Ryan)
Organization: INTERGRAPH (APD) -- Palo Alto, CA
Lines: 9

>Anybody else have suggestions on sets of systems for checking
>portability?  And how about portability between different system
>libraries and different terminal handling schemes, a problem we
>don't (yet) have because we ignore it?

I would think Vaxes, IBM-PCs, Suns, and Macs are somewhat incestuous.
If you have the money and are interested in the market, you might try
some radically different hardware and operating systems like mainframe
IBM, Cray, CDC, Fujitsu,.....