Xref: utzoo comp.misc:9575 comp.lang.misc:5174 Path: utzoo!utgpu!watserv1!watmath!att!rutgers!mit-eddie!bu.edu!xylogics!samsung!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!texbell!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.misc,comp.lang.misc Subject: Re: The CS "religion" (was Re: It looks like he's at it again!) Message-ID: Date: 16 Jul 90 14:48:59 GMT References: <1990Jul12.012730.4248@Stardent.COM> <64044@sgi.sgi.com> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Followup-To: comp.lang.misc Organization: Xenix Support, FICC Lines: 19 In article rang@cs.wisc.edu (Anton Rang) writes: > Portability is something which is not especially important most of > the time; on the other hand, it's rather difficult to write > non-portable code in many languages (C being one notable exception, > and of course any code using system routines or run-time libraries is > non-portable as well). You have to work at it, a bit. Well, it seems no two Modula-2 compilers have the same set of run-time libraries for I/O. Then there's Fortran, which is so constrained to the fixed-format card-image world that to do anything interesting with it from the point of view of the user interface you pretty much have to go right to the system. Pascal, of course, is aother case where a limited base standard has led to the use of massive numbers of non-portable extensions. Forth is a sitting duck, so I won't take a shot at it. ADA hasn't been around long enough to tell one way or the other, but I understand a lot of the DoD ADA code has become dependent on VRTX. To sum it up, I can't think of a single language in which it is the slightest bit difficult to write non-portable code. -- Peter da Silva. `-_-' +1 713 274 5180.