Trailing-Edge
-
PDP-10 Archives
-
SRI_NIC_PERM_FS_1_19910112
-
c/x3j11/x3j11.holey-mail
There are no other files named x3j11.holey-mail in the archive.
17-Nov-88 15:24:55-PST,3279;000000000000
Mail-From: KLH created at 17-Nov-88 15:19:22
Date: Thu, 17 Nov 88 15:18:38 PST
From: Ken Harrenstien <KLH@SRI-NIC.ARPA>
Subject: X3J11 mailing list
To: x3j11@SRI-NIC.ARPA
cc: klh@SRI-NIC.ARPA
Message-ID: <12447376021.25.KLH@SRI-NIC.ARPA>
I think I've received just about all the responses I'm going to get, so
here's the setup:
To send a message to everyone, mail to: X3J11@SRI-NIC.ARPA.
To request changes etc, use the usual: X3J11-REQUEST@SRI-NIC.ARPA.
I'm enclosing the current distribution list below, so you can see
who's on and who's not. You will probably find the format a bit odd,
but understandable (it's meant for direct reading by our TOPS-20
mailer). I've used domain name addresses whenever possible, which is why
many of them go through UUNET. If you know of a better address, or
have more people to add, please send your updates to X3J11-REQUEST.
I'm also keeping a log file of the messages, but it's not publicly
readable since I wasn't sure whether people wanted their discussions
open or not; SRI-NIC is a highly visible site. I'm also initially
assuming that this list is restricted to X3J11 members only, until
said members decide otherwise.
OK, have at it!
----------------------------
!---------- Valid addresses (sorted by domain name) -----------!
! Dave Prosser ! dfp@ATTUNIX.ATT.COM,-
! Douglas A. Gwyn ! Gwyn@BRL.MIL,-
! Jim Williams ! williams@CSS.NRL.NAVY.MIL,-
! Lu Anne Van de Pas ! vandepas@DEC-DECWET.DEC.COM,-
! Randy Meyers ! rmeyers@DEC-TLE.DEC.COM,-
! Art Bjork ! bjork@DEC-TLE.DEC.COM,-
! Andy Johnson ! andyj@ENX.PRIME.COM,-
! Mike Bennett ! mbennett@gould.UU.NET,-
! Walter Murray ! Walter@HPDA.HP.COM,-
! Shawn Elliott ! elliott@IBM.COM,-
! Mark Schisler (temporarily sharing Elliott's addr) ! elliott@IBM.COM,-
! Randy Hudson ! rgh@INMET.INMET.COM,-
! Clark Nelson ! clark@LANGLAB1.HF.INTEL.COM,-
! Chuck Rasbold (also at rasbold@ssi.uu.net) ! rasbold@LLL-LCC.LLNL.GOV,-
! Linda Stanberry ! linda@LLL-LCC.LLNL.GOV,-
! Dave Weil ! davewe@MICROSOFT.UU.NET,-
! Steve Davies ! srd@PEORA.CCUR.COM,-
! Zona Walcott ! zona@PYRPS5.PYRAMID.COM,-
! Ken Harrenstien ! KLH@SRI-NIC.ARPA,-
! Alan Fargusson ! alanf@SUN.COM,-
! Courtney Meissen ! cmeissen@SUN.COM,-
! Michael Eager ! eager@SUN.COM,-
! Carl Sutton ! sutton@TEKTRONIX.TEK.COM,-
! Steve Adamczyk ! jsa@EDG1.UU.NET,-
! Tom Plum ! plum@PLUMHALL.UU.NET,-
! Larry Jones ! scjones@SDRC.UU.NET,-
! Neal Weidenhofer ! nw@UTS.AMDAHL.COM,-
!-------------- Addresses not in domain format ----------------!
! Tom MacDonald ! "tundra!hall!tam"@SUN.COM,-
! (should be tam@tmacd.cray.com when CRAY.COM gets its act together) !
! Pete Darnell ! "stellar!pete"@UCBVAX.BERKELEY.EDU,-
! (trying pete@STELLAR.UU.NET) !
!------------- No answer, but may work -----------------------!
! Steve Adamski ! kordonov@ATTUNIX.ATT.COM,-
! Larry Breed ! "ibmpa!lmb"@UCBVAX.BERKELEY.EDU,-
!-------------- Unreachable, need path ------------------------!
! Craig Bordelon ! ! "pyuxe!!cjb3" !
! (UCB & SUN bounced; no response from UUNET) !
! Michael Meissner ! ! "mcnc!!rti!!xyzzy!!meissner" !
! (UCB & SUN bounced, no response from UUNET) !
! (note MCNC.ORG and RTI.RTI.ORG exist) !
-------
22-Dec-88 15:52:26-PST,3423;000000000000
Received: from research.att.com by SRI-NIC.ARPA with TCP; Thu, 22 Dec 88 15:47:41 PST
From: dfp@attunix.att.com
Date: Thu, 22 Dec 88 18:41 EST
To: attunix!sri-nic.arpa!x3j11
Subject: ANSI C draft reprinted just before being sent to X3
At essentially the last minute, a problem was found regarding
CLK_TCK when the ANSI C draft and POSIX are combined and the
pair are then matched against X/OPEN and SVID. Keeping the
story short, ANSI + (X/OPEN, SVID) => CLK_TCK == 1000000, but
(POSIX, /usr/group) + (X/OPEN, SVID) => CLK_TCK ~= 50 or 60 or 100.
In order to work around this minor problem (which appears that
it would have required a March meeting if it had not been fixed
now), the name CLK_TCK was changed to CLOCKS_PER_SEC in the ANSI C
draft. A new draft (dated December 7) was printed with a few
editorial changes, all approved unanimously by the draft review
subcommittee.
The new draft has two document numbers: 88-158 (without diffmarks)
and 88-159 (with diffmarks). The following is the list of changes
with October 31, 1988 references and approximate May 13, 1988
references:
Summary of changes since October 31st draft
Oct. 31 refs May 13 refs
Page Line(s) Page Line(s)
3 6-7 3 5-6 Definition of character changed to two
sentences. "Character -- a bit representation
that fits in a byte. The representation of
each member of the basic character set in both
the source and execution environments shall
fit in a byte."
25 19 24 ~17 Added a footnote (18) noting that array and
functions behave differently when qualified.
"See \(sc3.5.3 regarding qualified array and
function types."
35 21,28,30 34 20,27,29 "When an integer" -> "When a value with
integral type" (Note that line 20 was "When
an unsigned integer...".)
50 24 48 2 "other is a" -> "other is a pointer to a"
131 11 127 9-10 "mode instead may" -> "mode may instead"
(Full version of last sentence in paragraph:
"Opening (or creating) a text file with
update mode may instead open (or create) a
binary stream in some implementations.")
133 24 129 18 "A" -> "As noted above, a"
133 24 129 18 Delete " instead of a digit string"
(And delete " *" in the May draft.)
133 30 129 24 "Otherwise, it" -> "(It"
133 31 129 24 "-justified." -> "-justified if this flag is
not specified.)"
(Full version of the new sentence: "(It will
be right-justified if this flag is not
specified.)")
133 33 129 25 "Otherwise, it" -> "(It"
133 33 129 25 "converted." -> "converted if this flag is
not specified.)"
(Full version of the new sentence: "(It will
begin with a sign only when a negative value
is converted if this flag is not specified.)")
171 10 166 10 "CLK_TCK" -> "CLOCKS_PER_SEC"
172 5 167 5 "CLK_TCK" -> "CLOCKS_PER_SEC"
175 41,44 170 40,43 "year (" -> "year (the first "
194 27 189 27 "CLK_TCK" -> "CLOCKS_PER_SEC"
200 28.5 195 27.5 Add "\(bu A structure or union is defined as
containing only unnamed members (\(sc3.5.2.1)."
211 6 205 33 "CLK_TCK" -> "CLOCKS_PER_SEC"
217 41 212 38 "4.1.2" -> "4.1.2.1"
You should be receiving your copy of the draft and rationale within a
week or so.
Dave (your friendly Redactor) Prosser
30-Jan-89 11:06:32-PST,2421;000000000000
Received: from uunet.UU.NET by SRI-NIC.ARPA with TCP; Mon, 30 Jan 89 10:37:12 PST
Received: from plumhall.UUCP by uunet.UU.NET (5.61/1.14) with UUCP
id AA02333; Mon, 30 Jan 89 13:37:15 -0500
From: plumhall!root@uunet.UU.NET
Message-Id: <8901301837.AA02333@uunet.UU.NET>
To: X3J11@SRI-NIC.ARPA
Date: Mon Jan 30 08:47:51 1989
X3J11/89-008
January 25, 1989
****************************
* IMPORTANT !!!!! *
* MEETING CHANGE NOTICE *
****************************
Dear X3J11 Members,
This is the official notice that we will NOT be having our
tentatively scheduled March 6-7, 1989 X3J11 meeting in
Seattle, Washington.
The primary reason for cancelling the March meeting is that
the X3 ballot on our draft will not close until March 3rd.
(There were various delays in the handling of the documents
by the X3 Secretariat.) If, as we all hope, there are no
negative X3 ballots, we would have lost the primary reason
for the meeting. However, at that point, it would be too
late to cancel the meeting.
The meeting is being tentatively resceduled for April 10-11,
1989. Microsoft continues to show great patience with our
dynamic scheduling and has agreed to host the April meeting
in Seattle. Hotel information will be coming in a later
mailing.
We are not certain that we will have the April meeting. It
depends on how the X3 ballot goes and what other business we
may need to deal with at that time. For example, there are
still some problems in the International arena. We
may also want to plan our approach to the maintenance phase
which we, hopefully, will soon be entering.
I will pass on the results of the balloting as soon as they
become available. I will pass on definite meeting plans as
soon as possible after that.
The new meeting date is the same as our original meeting
schedule so I hope that it will not cause too many conflicts
with your plans. I apologize for any inconvenience that
this may cause you.
Thanks for your continued patience and support.
Sincerely,
Jim Brodie
X3J11 Chair
6-Feb-89 11:36:30-PST,3356;000000000000
Received: from BCO-MULTICS.HBI.HONEYWELL.COM by SRI-NIC.ARPA with TCP; Mon, 6 Feb 89 11:29:10 PST
Date: Mon, 6 Feb 89 14:04 EST
From: Warren Johnson <WJohnson@BCO-MULTICS.HBI.HONEYWELL.COM>
Subject: interpretation request
To: x3j11@SRI-NIC.ARPA
Message-ID: <890206190424.714126@BCO-MULTICS.HBI.HONEYWELL.COM>
X3J11/89-010
Tuesday, January 31, 1989
Thomas Plum
Vice Chair ANSI X3-J11
Plum Hall
1 Spruce Ave
Cardiff, NJ 08232
Dear Mr Plum:
A syntactic ambiguity exists in the dpANS C standard for which
there appears to be no semantic disambiguation. A sequence of
examples should explain the ambiguity. This matter needs
interpretation by the ANSI X3-J11 committee.
For these examples, let T be declaration specifiers which contain
at least one type specifier, to satisfy the semantics from 3.5.6:
"If the identifier is redeclared in an inner scope ..., the type
specifiers shall not be omitted in the inner declaration."
Let U be an identifier which is a typedef name at outer scope and
has not (yet) been redeclared at current scope. A caret indicates
the position of each abstract declarator. Consider this declaration:
declaration-specifiers direct-declarator (T (U));
^
Here U is the type of the single parameter to a function
returning type T, due to a constraint from 3.5.4.2:
"In a parameter declaration, a single typedef name in parentheses is
taken to be an abstract declarator that specifies a function with a
single parameter, not as redundant parentheses around the identifier
for a declarator."
Consider this declaration:
declaration-specifiers direct-declarator (T (U (parameter-type-list)));
^ ^
In this example, U could be the type returned by a function which
takes parameter-type-list. This in turn would be the single
parameter to a function returning type T.
Alternatively, U could be a redundantly parenthesized name of a
function which takes parameter-type-list and returns type T.
Given the spirit of the constraint from 3.5.4.2, the former
interpretation seems to be that intended by ANSI. If so, the
constraint may be changed to something similar to:
"In a parameter declaration, a direct declarator which redeclares a
typedef name shall not be redundantly parenthesized."
Of course, parentheses must not be disallowed entirely. Consider
this unambiguous redeclaration of typedef name U:
declaration-specifiers direct-declarator (T (* U)(parameter-type-list));
If you require more information or discussion on this matter,
please contact me, at (508) 671-4156, or by mail at the indicated
address, M/S 826A. Your prompt consideration of this matter is
greatly appreciated.
Sincerely,
Bruce Blodgett
Senior Software Engineer
Compiler Development
Bull HN Information Systems Inc.
300 Concord Road
Billerica, MA 01821
6-Apr-89 05:16:32-PDT,562;000000000000
Mail-From: KLH created at 6-Apr-89 05:10:26
Date: Thu, 6 Apr 89 05:10:21 PDT
From: Ken Harrenstien <KLH@SRI-NIC.ARPA>
Subject: Seattle meeting
To: x3j11@SRI-NIC.ARPA
cc: klh@SRI-NIC.ARPA
Message-ID: <12483954523.17.KLH@SRI-NIC.ARPA>
Just out of curiousity, I'm wondering how many people are planning to
attend this meeting (April 10-11) and whether there will actually be
anything to vote on. Unfortunately I have too many conflicts to go
myself and don't have an alternate, but perhaps it doesn't matter as
much as it used to?
--Ken
-------
25-Apr-89 14:44:36-PDT,909;000000000000
Received: from uunet.uu.net by SRI-NIC.ARPA with TCP; Tue, 25 Apr 89 14:33:41 PDT
Received: from sdrc.UUCP by uunet.uu.net (5.61/1.14) with UUCP
id AA06531; Tue, 25 Apr 89 16:03:48 -0400
From: sdrc!scjones@uunet.UU.NET (Larry Jones)
Message-Id: <8904252003.AA06531@uunet.uu.net>
Received: by sdrc; Tue, 25 Apr 89 15:56:17 edt
Date: Tue, 25 Apr 89 15:56:17 edt
To: uunet!SRI-NIC.ARPA!X3J11@uunet.UU.NET
Subject: C Binding for GKS-3D
I have just received the current draft of the proposed C Language
Binding for GKS-3D. If anyone is interested in reviewing it, let
me know and I'll be glad to send you a copy.
----
Larry Jones UUCP: uunet!sdrc!scjones
SDRC scjones@sdrc.UU.NET
2000 Eastman Dr. BIX: ltl
Milford, OH 45150 AT&T: (513) 576-2070
"When all else fails, read the directions."