X3J11 response to comments (was: Block Closure)

Doug Gwyn gwyn at brl-smoke.ARPA
Mon Apr 25 04:28:57 AEST 1988


In article <1988Apr24.000653.2627 at utzoo.uucp> henry at utzoo.uucp (Henry Spencer) writes:
>At risk of starting another flame war, if this is a problem, the function in
>question is too complex and should be split up into more manageable pieces.

FLAME ON!

You have managed to denigrate the majority of code written by
people at our installation!  How dare you aver that there are
"good" styles vs. "bad" ones??  Don't you know that any old
code that seems to work is good enough???  People like you
should keep their mouths shut, instead of casting aspersions
on my organization!!!!

FLAME OFF:-)

(I thought I would save somebody the trouble.)

Hi, Henry!  Thanks for the draft comments.  The official X3J11
response-to-second-public-review document is scheduled to be sent
to CBEMA no later than 23-May-1988, and CBEMA will then mail copies
to the correspondents.  There will be a third public review of the
draft proposed standard starting at approximately the same time.
This time, X3J11 intends to limit comments in the third round to
those pertaining to changes made to the proposed standard at the
April 1988 meeting, plus any complaints from second-round commentors
that their issues had not been adequately addressed.  It is hoped
that the contents of the final standard will be determined by the
end of the August 1988 meeting.

(This means that it is now too late to propose new inventions,
unless you can discover a major problem that somehow has been
overlooked thus far and persuade the committee that it has to
be fixed.)

Also, thanks to those who sent me electronic copies of their public
comments.  That really helped speed up the data entry aspect of the
April meeting.  There were 36 formal comment letters registered via
CBEMA (hundreds of comments), plus several that somehow missed the
registration date but that I carried to the meeting with me (that
probably did not improve my popularity within the committee).  By
working overtime, using several computers on-site for data entry,
X3J11 somehow managed to consider all comments and discuss issues
that needed it in full committee.  I wouldn't have thought it
possible..



More information about the Comp.lang.c mailing list