Actions arising from October 2000 Austin-59 Page 1 of 1 Submitted by Andrew Josey, The Open Group. October 16th, 2000 Action Items arising from the October plenary meeting (c99 defect tracking) 2000-10-01 ACTION: AJ to talk to John Benito to ensure all C99 defect resolutions are incorporated CLOSING: Mail sent to John Benito on October 16. (document style) 2000-10-02 ACTION Donn Terry and Don Cragun to consider the use of fonts (in particular CW) and why they differ from POSIX. CLOSED (references) 2000-10-03 ACTION Yvette to check placement of references (normative & informative) (request formal resolution to drop getipnodebyaddr, getipnodebyname and freehostent functions) 2000-10-04 ACTION TOG OR to request OGTGBase discuss ERN 49 and provide a resolution permitting the dropping of these functions. (time issues) 2000-10-05 ACTION Glen Seeds to provide rationale explaining why the POSIX clock is the way the way it is and what are the consequences CLOSED (covered by 2000-10-06) (more time issues) 2000-10-06 ACTION Donn Terry to rephrase definition sentence "Whether and how ...", line 3495) to deal with leap seconds CLOSED Replace 3495 with: The relationship between the actual time of day and the current value for Seconds Since the Epoch is unspecified. How any changes to the value of Seconds Since the Epoch are made to align to a desired relationship with the current actual time are made is implemetation-defined. As represented in Seconds Since the Epoch, each day shall be accounted for by exactly 86400 seconds. Add to rationale (repl 1463): The topic of whether Seconds Since the Epoch should account for leap seconds has been debated upon a number of occasions, and each time consensus was reached (with acknowleged dissent each time) that the majority of users are best served by treating all days identically. (That is, the majority of applications were judged to assume a single length (as measured in Seconds Since the Epoch) for all days.) Those applications which do care about leap seconds can determine how to handle them in whatever way it felt was best for that application. This was particularly emphasized because there was disagreement about what the best way of handling leap seconds might be. It is a practical impossiblity to mandate that a conforming implementattion must have a fixed relationship to any particular official clock (consider isloated systems, or systems performing "reruns" by setting the clock to some arbitrary time). Note that as a practical consequence of this, the length of a second as measured by some external standard is not specified. Applications must be matched to a system that provides the particular handling of external time in the way required by the application. (cannot vs can not, a matter of style) 2000-10-07 ACTION Yvette to confirm that "cannot" is an acceptable term (LC_TIME XSI functionality) 2000-10-08 ACTION AJ to reword introduction to 7.3.5.2 to show that the entire section is XSI (environment variables and leading digits) 2000-10-09 ACTION Glen Seeds to propose new wording to cover the problem of environment variables with leading digits. CLOSED - Editors have notes (provision of rationale for int8_t, uint8_t etc) 2000-10-10 ACTION Andrew Gollan to provide rationale on making exact width integer types mandatory (missing interpretation) 2000-10-11 ACTION AJ to encourage 1003.1 interp group to finalize 101. 2000-10-12 ACTION Andrew Gollan to provide a definition of symbolic names/macros etc. 2000-10-13 ACTION Fred Tydeman to propose suitable equations for float.h 2000-10-14 ACTION Nick Stoughton to propose scope extension for isfdtype() for other file types as strawman. CLOSED 2000-10-15 ACTION Nick Stoughton to request Usenix gurus for input on SCCS grammar. See XCU ERN 46 2000-10-16 ACTION Don Cragun to provide specific words for TZ usage in XCU ERN 48 CLOSED: The following changes are intended to address the concerns raised by Jon Hitchcock in XCU6d4 ERN 48: [AJ comment, we will need to identify appropriate CH here to flag changes] at: Add new entry after P2350, L21846: TZ Determine the timezone used to calculate date and time strings written by ar -tv. If TZ is unset or null, an unspecified default timezone shall be used. [AJ add CH: The TZ entry is added to the ENVIRONMENT VARIABLES section] date: Change "not set" on P2508, L11294 to "unset or null". Change "not set" on P2511, L11410 to "unset or null". diff: Delete " the locale for affecting" from P2530, L12169. Add new sentence to end of P2530, L12170: If TZ is unset or null, an unspecified default timezone shall be used. ipcs: Change: time strings written by ipcs. on P2724, L19603 to: date and time strings written by ipcs. If TZ is unset or null, an unspecified default timezone shall be used. lp: Add new entry after P2776, L21607: TZ Determine the timezone used to calculate date and time strings displayed in the lp banner page, if any. If TZ is unset or null, an unspecified default timezone shall be used. [AJ add CH: The TZ entry is added to the ENVIRONMENT VARIABLES section] ls: Add new sentence to end of P2781, L21846: If TZ is unset or null, an unspecified default timezone shall be used. mailx: Add new entry after P2797, L22488: TZ This variable may determine the timezone used to calculate date and time strings written by mailx. If TZ is unset or null, an unspecified default timezone shall be used. [AJ add CH: The TZ entry is added to the ENVIRONMENT VARIABLES section] pax: Add new entry after P2920, L27332: TZ Determine the timezone used to calculate date and time strings when the -v option is specified. If TZ is unset or null, an unspecified default timezone shall be used. [AJ add CH: The TZ entry is added to the ENVIRONMENT VARIABLES section] pr: Change: for use in writing header lines. on P2724, L19603 to: used to calculate date and time strings written in header lines. If TZ is unset or null, an unspecified default timezone shall be used. ps: Add new entry after P2861, L29066: TZ Determine the timezone used to calculate date and time strings displayed. If TZ is unset or null, an unspecified default timezone shall be used. [AJ add CH: The TZ entry is added to the ENVIRONMENT VARIABLES section] qalter: Delete P2975, L29624. Change P2975, L29626-29627 to: TZ Determine the timezone used to interpret the date-time option-argument. If TZ is unset or null, an unspecified default timezone shall be used. [AJ comment add CH: The TZ entry is added to the ENVIRONMENT VARIABLES section] qdel: Delete P2927, L29762. Delete P2979, L29764-29765. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] qhold: Delete P2982, L29889. Delete P2982, L29891-29892. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] qmove: Delete P2985, L29982. Delete P2985, L29984-2998 [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] qmsg: Delete P2988, L30087. Delete P2988, L30089-30090. qrerun: Delete P2991, L30182. Delete P2991, L30184-30185. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] qrls: Delete P2993, L30294. Delete P2993, L30296-30297. qselect: Change "\fIdate_time\fP on P2996, L30391 to "\fItime\fP". Delete P3001, L30609. Change P3001, L30611-30612 to: TZ Determine the timezone used to interpret the date-time option-argument. If TZ is unset or null, an unspecified default timezone shall be used. qsig: Delete P3005, L30740. Delete P3005, L30742-30743. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] qstat: Delete P3008, L30864. Delete P3008, L30867-30868. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] qsub: Change "\fIdate_time\fP on P3012, L30999 to "\fItime\fP". Delete P3020, L31328. Change P3020, L31334-31335 to: TZ Determine the timezone used to interpret the date-time option-argument. If TZ is unset or null, an unspecified default timezone shall be used. touch: Add new sentence to end of P3131, L35448: If TZ is unset or null, an unspecified default timezone shall be used. uucp: Delete P3180, L37156. Delete P3180, L37158. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] uustat: Delete P3191, L37544. Delete P3191, L37546. [AJ comment add CH: The LC_TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section] 2000-10-17 ACTION Donn Terry to provide detailed aardvark required for XCU ERN 185. CLOSED 2000-10-18 ACTION Don Cragun to provide detailed aardvark for interp 188 on 1003.2 2000-10-19 ACTION Donn Terry to provide detailed aardvark to remove lisp mode from ex/vi. CLOSED 2000-10-20 ACTION Donn Terry to contact Keith Bostic (bostic@bsdi.com) regarding ERN 185 (ex -s) for sanity check. 2000-10-21 ACTION TOG OR to request OGTGBase clarify wording for make regarding XCU ERN 417 (pax logical records rather than physical blocks) 2000-10-22 ACTION Donn Terry to refine aardvark and propose precise rewording for XCU ERN 478. 2000-10-23 ACTION Keld Simonsen to provide aardvark with specific changes required for glyph v character in XCU ERN 480 2000-10-24 ACTION Donn Terry to provide additional paragraph explaining why certain tabs features are XSI only. (test rationale) 2000-10-25 ACTION Donn Terry to provide aardvark to add new rationale for XCU ERN 578, showing XSI support. (uucp app usage) 2000-10-26 ACTION OG OR to request resolution from OGTGBase for normative requirement in App Usage of uucp - XCU ERN 600. 2000-10-27 ACTION Donn Terry to propose more detailed changes for vi and more re logical v physical lines. XCU ERN 626 2000-10-28 ACTION Donn Terry to contact Keith Bostic to discuss XCU ERN 646 and if necessary submit a new interpretation request against .2. 2000-10-29 ACTION Donn Terry to file interpretation request against .2b regarding XCU ERN 679, SIGINT v ESC in vi. 2000-10-30 ACTION Andrew Josey to file interp request against .2b regarding the -P option to cp, which appears to be missing. 2000-10-31 ACTION Mark Brown to propose detailed aaardvark to clarify join reviewers note on p 2734 of D4. 2000-10-32 ACTION Nick Stoughton to discuss both m4 reviewers notes with Eric Allman. 2000-10-33 ACTION Andrew Josey to file an interpretation request for pax. See reviewers note on p2926. 2000-10-34 ACTION Don Cragun to provide text for reviewers note on p 3060, sh and large files. CLOSED The following notes are intended to address the concerns raised by Donn Terry in XCU6d3 ERN 215 and noted in the Notes to Reviewers on XCU6d4 P3060, L32744-32747: For reference, XCU6d3 ERN 215 is included at the end of this file. Mr. Terry says that he doesn't see anything in stat() that permits it to fail on a very large file. The text that allows this to happen is the EOVERFLOW error on XSH6d4, P1912, L4343387-43389. (In a 32-bit application running on an implementation where the struct stat st_size member's off_t type is a 32-bit long value, but large file sizes will not fit in an 32-bit off_t, these lines require that either the shell be built as a greater than 32-bit application, use the transitional interfaces specified in the Large Files Summit Specification, or use some non-standard means of assuring that it can resolve the pathnames of largefiles even though the standard stat() function may fail with EOVERFLOW due to file size limitations.) Thus, it is the size of the file that matters, not the length of the file's name. Mr. Terry's proposed resolution includes three possible actions. They are to change XCU6d4 P3060, L32743 from: "Path name expansion does not fail due to the size of a file." to: 1. "Path name expansion shall not fail due to the size of a file name.", 2. "On some systems, errors might occur during pathname expansion that are caused by the presence of very large files. The implementation shall take the necessary precautions to assure that such failures do not impact the correct operation of sh.", or 3. "Path name expansion shall not fail due to the size of a file name. On some systems, errors might occur during pathname expansion that are caused by the presence of very large files. The implementation shall take the necessary precautions to assure that such failures do not impact the correct operation of sh." The Large Files Summit (and SUSv2 and this draft) do not require that the shell be able to support file redirection on large files and does not require that most utilities be able to handle large files. See XCU6 subclause 1.12 Considerations for Utilities in Support of Files of Arbitrary Size (XCU6d4 P2232-2233) for details. I suggest that we change "does not fail" on P3060, L32743 to "shall not fail" as part of the shallification process, and delete the Notes to Reviewers from P3060, L32744-32747. _____________________________________________________________________________ COMMENT Enhancement Request Number 215 donnte@microsoft.com Bug in XCUd3 (rdvk# 207) [DT-XCU-177] Mon, 1 May 2000 11:55:26 -0700 _____________________________________________________________________________ Accept_____ Accept as marked below_X___ Duplicate_____ Reject_____ Rationale for rejected or partial changes: Add a reviewers note with the problem statement _____________________________________________________________________________ Page: 888 Line: 33990 Section: sh Problem: I objected to this one last time, and this still isn't at all clear. I *may* (??) understand what the response was driving at, but the text here (at least in the absence of corresponding rationale) is simply unclear (at least out of context... again "interpretation bait".) (Something about the LFS and stat() not failing.) There is nothing I see under the stat() command that permits it to fail on a very large file (although that is a dicey area). If a potentially standards violating (because stat() fails) behavior is being special cased, it can't be said in this little text. Based on what's there.... The size of the file doesn't matter, it's its the size of the name. (Also, shallify.) Action: Choose one or both: "does not fail due to the size of a file" -> "shall not fail due to the size of a file name". OR On some systems, errors might occur during pathname expansion that are caused by the presence of very large files. The implementation shall take the necessary precautions to assure that such failures do not impact the correct operation of sh. _____________________________________________________________________________ 2000-10-35 ACTION Andrew Josey to identify and request status for interpretation referred to in XSH ERN 31 2000-10-36 ACTION TOG OR to request new words for STREAMS to resolve XSH ERN 32. (thread cancellation) 2000-10-37 ACTION Frank Prindle to resubmit lost interpretation request for XSH ERN 44 (maths functions) 2000-10-38 ACTION Fred Tydeman to submit a proposal for aligning with C99 annex F and annex G. (aio_fsync and use of the aiocbp structure) 2000-10-39 ACTION Mark Brown to file interpretation request against .1 1996 to clarify direction for XSH ERN 55. (range expressions) 2000-10-40 ACTION Glen Seeds to locate "range expression" usage and prepare edit instructions to make it clear that the use of range expressions outside of the POSIX locale produces unspecified results (XBD ERN 83, 154 and 165) 2000-10-41 ACTION Donn Terry to file a defect report on single-byte (XBD ERN 116) with WG14 2000-10-42 ACTION Andrew Josey to file interp against .2b regarding character set definitions, lines 3969-3981. (ordering paragraphs within man pages with multiple functions) 2000-10-43 ACTION Donn Terry to provide other reorderings as promised for XSH ERN 80 2000-10-44 ACTION TOG OR to ask OGTGBase for clarification on XSH ERN 103 2000-10-45 ACTION Ulrich Drepper to provide change text for the c99 page w.r.t. falling off the end of main(). (how to use fchdir and grantpt portably) 2000-10-46 ACTION TOG OR to ask OGTGBase how to get a file desc for fchdir() portably and how to get an fd for grantpt. 2000-10-47 ACTION Fred Tydeman to raise the matter of the return type from main() with WG14 and to create a defect report if necessary. CLOSED The C standard permits implementation defined main's. 2000-10-48 ACTION Andrew Gollan to provide rationale for socklen_t type and its use. 2000-10-49 ACTION Donn Terry to locate all "conversion characters" references and propose required font changes. (fseek error, EPIPE vs ESPIPE) 2000-10-50 ACTION TOG OR to request OGTGBase examine XSH ERN 170 (EPIPE v ESPIPE from fseek) 2000-10-51 ACTION Andrew Gollan to address problems in XSH ERN 185 (GAI_ error numbers) 2000-10-52 ACTION Ulrich Drepper to check the use of restrict in XSH ERN 202 and 203 (name for a pseudotty, or how to get a fd on pseudotty portably) 2000-10-53 ACTION TOG OR to ask OGTGbase about XSH ERN 208 (setjmp, macro or not? ) 2000-10-54 ACTION Frank Prindle to file defect report on ISO C for XSH ERN 239 (poll man page and shading) 2000-10-55 ACTION TOG OR to ask OGTGbase about XSH ERN 254 (posix_spawn_file_actions_addclose) 2000-10-56 ACTION Frank Prindle to submit interpretation request for XSH ERN 258 (trace functions) 2000-10-57 ACTION Frank Prindle to ask the PASC realtime group about XSH ERN 268 and 274 2000-10-58 ACTION Andrew Josey to reword seekdir rationale supplied in action 2000-05-033