Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!uiucdcsb!johnston
From: johnston@uiucdcsb.UUCP
Newsgroups: comp.lang.c++
Subject: Re: C++ fine for work now??
Message-ID: <165700004@uiucdcsb>
Date: Fri, 20-Feb-87 14:12:00 EST
Article-I.D.: uiucdcsb.165700004
Posted: Fri Feb 20 14:12:00 1987
Date-Received: Mon, 23-Feb-87 01:40:31 EST
References: <43105@beno.seismo.CSS.GOV>
Lines: 23
Nf-ID: #R:beno.seismo.CSS.GOV:43105:uiucdcsb:165700004:000:883
Nf-From: uiucdcsb.cs.uiuc.edu!johnston    Feb 20 13:12:00 1987


>/* ---------- "C++ fine for work now??" ---------- */
>Until I can get C++ up on a non-VAX (read SUN 3/160) without
>making a career of it,  C++ is NOT fine for work now, no
>matter how badly I want to use it (which is pretty badly).
> ...

I disagree.  The fact that C++ is implemented as a front-end to
the C compiler is a big win.  I "ported" C++ version 1.1 to our Encore
Multimax (NS32000 series based shared memory multiprocessor running under
4.2bsd Unix (UMAX)) in under 3 hours.  It is serving well as an OS
development language.  I can't believe that it would be very difficult
to port to a MC68000 series based 4.2bsd system.

Gary Johnston
Department of Computer Science
University of Illinois at Urbana-Champaign
1304 West Springfield Avenue
Urbana, IL 61801

USENET:	{pur-ee,convex,ihnp4}!uiucdcs!johnston
ARPA:	johnston@b.cs.uiuc.edu
CSNET:	johnston%uiuc@csnet-relay