Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!princeton!allegra!ulysses!gamma!pyuxww!pyuxe!joecar
From: joecar@pyuxe.UUCP
Newsgroups: comp.lang.c
Subject: Portable C vs Efficient C or "Cost of Portability"
Message-ID: <213@pyuxe.UUCP>
Date: Wed, 1-Apr-87 22:17:00 EST
Article-I.D.: pyuxe.213
Posted: Wed Apr  1 22:17:00 1987
Date-Received: Sat, 4-Apr-87 11:43:02 EST
Organization: Bell Communications Research
Lines: 19
Keywords: portability, performance


I'm looking for some information, experiences, opinions,
references, etc., that will help me understand the following
question:
 
   If one writes portable C, does it have to be less efficient 
   than non-portable C ?
 
In other words, does writing portable code add to the run time
overhead?  Conversely, can I write non-portable code that is
more efficient than the portable counterpart?

My project is looking at the "cost of portability", and would
appreciate any information (or journal references, etc.) that
reference any studies on the efficiency of portable C code.
Thanks in advance.
 
Joe Carfagno
...!bellcore!pyuxe!joecar