Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!vaxine!wjh12!genrad!grkermit!masscomp!clyde!burl!ulysses!mhuxl!ihnp4!drutx!houxe!hogpc!houxm!houxz!vax135!floyd!cmcl2!seismo!brl-tgr!brl-vgr!gwyn
From: gwyn@brl-vgr.UUCP
Newsgroups: net.lang.c
Subject: Re: Numerical C and C++
Message-ID: <2780@brl-vgr.UUCP>
Date: Fri, 1-Jun-84 14:39:24 EDT
Article-I.D.: brl-vgr.2780
Posted: Fri Jun  1 14:39:24 1984
Date-Received: Thu, 7-Jun-84 00:17:06 EDT
References: <1311@mhuxt.UUCP> <5300001@hpdcdb.UUCP>, <1945@rlgvax.UUCP> <2811@alice.UUCP>, <1973@rlgvax.UUCP>, <Re: Numerical C
Lines: 16

Relay-Version: version B 2.10 5/3/83 based; site houxm.UUCP
Posting-Version: version B 2.10.1 6/24/83; site brl-vgr.ARPA
Message-ID: <2780@brl-vgr.ARPA>
Date: Fri, 1-Jun-84 14:39:24 EDT
Date-Received: Sat, 2-Jun-84 15:49:39 EDT

 and C++
Organization: Ballistics Research Lab
Lines: 6

This flaming contest would have been avoided if brucee would've been
informative the first time around, rather than just knocking someone
who is TRYING to share what little is known about the evolution of C
inside of AT&TBL.  Many of us care quite a bit about what happens to
C in the next several years; how about an informative dialogue about
the current and near-term changes in the C language, folks?