Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!styx!ptsfa!ihnp4!inuxc!pur-ee!uiucdcs!uiucdcsb!kenny
From: kenny@uiucdcsb.cs.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: C vs assembler, or, Here We Go
Message-ID: <165600001@uiucdcsb>
Date: Mon, 27-Apr-87 23:03:00 EDT
Article-I.D.: uiucdcsb.165600001
Posted: Mon Apr 27 23:03:00 1987
Date-Received: Thu, 30-Apr-87 04:17:40 EDT
References: <382@bms-at.UUCP>
Lines: 30
Nf-ID: #R:bms-at.UUCP:382:uiucdcsb:165600001:000:1424
Nf-From: uiucdcsb.cs.uiuc.edu!kenny    Apr 27 22:03:00 1987


/* Written 12:50 pm  Apr 24, 1987 by stuart@bms-at.UUCP in uiucdcsb:comp.lang.c */
/* ---------- "Re: C vs assembler, or, Here We Go" ---------- */
[...] our people can still turn out a full featured  data
entry  program using assembler in only 15 minutes as opposed to 2
hrs for 'C'.  The difference is that  our  'C'  library  has  not
evolved  to  the  extent  that  the  assembler  library has.  (An
assembler data entry program consists of some  table  definitions
via macros and some subroutine hooks to implement deviations from
standard features.)
-- 
Stuart D. Gathman	<..!seismo!dgis!bms-at!stuart>
/* End of text from uiucdcsb:comp.lang.c */

Sounds as if what you need is a set of interface adapters to make your
assembler library callable by C programs.  And, speaking from
experience, it is astounding what improvements in productivity can
result by making an existing mature library available to any ``new''
language; not only does it make all the existing functions available,
but it also means that the programmers can apply what they know about
the old library's quirks.

Moral: Choose a run-time environment that allows interlinking all your
languages.

Kevin Kenny			UUCP: {ihnp4,pur-ee,convex}!uiucdcs!kenny
Department of Computer Science	ARPA: kenny@B.CS.UIUC.EDU (kenny@UIUC.ARPA)
University of Illinois		CSNET: kenny@UIUC.CSNET
1304 W. Springfield Ave.
Urbana, Illinois, 61801		Voice: (217) 333-8740