Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!cmcl2!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.lang.c
Subject: Re: HARRIS FLAME Re: SHORT vs. INT
Message-ID: <1775@brl-tgr.ARPA>
Date: Fri, 27-Sep-85 16:12:29 EDT
Article-I.D.: brl-tgr.1775
Posted: Fri Sep 27 16:12:29 1985
Date-Received: Mon, 30-Sep-85 00:48:42 EDT
References: <1390@brl-tgr.ARPA> <2778@sun.uucp> <519@lasspvax.UUCP> <2803@sun.uucp> <699@othervax.UUCP> <229@3comvax.UUCP>
Organization: Ballistic Research Lab
Lines: 11

Both portability and abstraction are worthwhile design goals.

One can write code using nice data abstraction in Jovial,
but this would probably be a mistake.

One could write highly portable code that cannot be maintained
due to its internal complexity, and this would also be a mistake.

"Portability" should be thought of in a fairly broad sense,
including "portability to other systems" (traditional meaning)
and "portability into the future" (important but often ignored).