Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ll-xn!cullvax!drw
From: drw@cullvax.UUCP
Newsgroups: comp.lang.c
Subject: Types
Message-ID: <1214@cullvax.UUCP>
Date: Tue, 26-May-87 17:31:35 EDT
Article-I.D.: cullvax.1214
Posted: Tue May 26 17:31:35 1987
Date-Received: Wed, 27-May-87 05:30:51 EDT
Organization: Cullinet Software, Westwood, MA, USA
Lines: 26

hrubin@osupyr.UUCP (Herman Rubin) writes:
>  What we people who can program using the power of the computer really need
> to do is convince the X3J11 committee to accept the idea that overloaded
> operators, defining of new types (not like C++), defining of operator
> symbols corresponding to operations not included in the default language,
> forcing inline, substitution of compiler-determined locations in inserted
> assembler instructions, and other versatile devices, and in general enabling
> the production of good semi-portable code is worthwhile.

One problem is that ANSI is only into standardizing existing practice.
In several parts of their rationale they note that there is
"insufficient experience" with a particular concept, and thus, they
won't include it in the standard.  (This hasn't stopped them from
adding a few totally new features, though.  But they are features that
are despirately needed.)  What we need is for someone to add these
features into a respected compiler and distribute it, so we can see
how these ideas work in practice.  Unfortunately, the commercial
outfits aren't interested in advancing the state of the art.  "He who
is out in front gets shot in the back."

Dale
-- 
Dale Worley		Cullinet Software
UUCP: ...!seismo!harvard!mit-eddie!cullvax!drw
ARPA: cullvax!drw@eddie.mit.edu
Un*x (a generic name for a class of OS's) != Unix (AT&T's brand of such)