Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!uxc!uxc.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: Third public review of X3J11 C
Message-ID: <225800053@uxe.cso.uiuc.edu>
Date: 23 Aug 88 13:07:00 GMT
References: <8365@smoke.ARPA>
Lines: 15
Nf-ID: #R:smoke.ARPA:8365:uxe.cso.uiuc.edu:225800053:000:704
Nf-From: uxe.cso.uiuc.edu!mcdonald    Aug 23 08:07:00 1988



>The fundamental problem is that IT IS MUCH TOO LATE to be making
>significant changes to the proposed standard.  Look at all the trouble

>I suggest that you GET INVOLVED in drafting
>the NEXT (revised) standard.

The problem is, how does one do this? IF you are a regular reader of this
august information dispersal system, you might here about some such
effort not too late after it gets started. But, in the absence of that,
you are going to know about it only AFTER the standard gets approved,
when the next version of your compiler comes out and your programs
stop compiling. I never heard about Fortran 77 until my programs
refused to run because a new compiler didn't support Hollerith fields.