Draft Minutes of October 2000 Meeting (Austin M6) AUSTIN/57 (DRAFT) 1. Opening & Introductions Welcome to the 6th Joint PASC/TOG/WG15 Revision Group meeting. Andrew Josey 1.1 Introductions 1.1.1 Attendance list Name Position Email Andrew Josey Chair, TOG/PASC ajosey@opengroup.org Frank Prindle DoD, TOG/PASC prindle@voicenet.com Cathy Hughes Editor, TOG c.hughes@opengroup.org Don Cragun Sun, TOG/PASC dwc@eng.sun.com Nick StoughtonSecretary, nick@usenix.org PASC/WG15/TOG Andrew Gollan Sun, TOG (XNET) adjg@eng.sun.com Ulrich DrepperRed Hat ulrich@redhat.com Mark Brown IBM, TOG mbrown@austin.ibm.com Keld Simonsen DKUUG, WG15 keld@dkuug.dk Finnbarr Compaq, TOG finnbarr.murphy@compaq.com Murphy Glen Seeds Cognos, WG15 glen.seeds@cognos.com Raja Oracle raja.srinivasan@oracle.com Srinivasan Fred Tydeman tydeman@tybor.com Jim Meyering Lucent meyering@lucent.com Donn Terry Microsoft donnte@microsoft.com Michael Oracle Michael.Kavanaugh@oracle.com Kavanaugh Bouazza Compaq bouazza.bachar@compaq.com1 Bachar Joanna Sun joanna.farley@uk.sun.com Farley Jay Ashford IBM ashford@austin.ibm.com Gary Miller IBM gwm@us.ibm.com 1.2 Approve Agenda The agenda (AUSTIN/55) was approved without addition. 1.3 Approval of Minutes The minutes of the previous meeting (May, AUSTIN/46) were approved after [heated] discussion on their completeness. The secretary agreed to try harder to capture all the discussions. 1.3.1 Matters Arising - Action Item Review 2000-05-001 Chair to discuss formal approval of JDOCS procedures with chair of JDOCS (Roger Martin) CLOSED: The JDOCS procedures have been forwarded to the three participating organizations for approval , where they have now been approved. 2000-05-002: WG15 OR to ensure convenor forwards info to SC22. CLOSED: This has been done via email. 2000-05-003: Chair to propose a timeline and plan for the .1q integration. CLOSED: The chair has communicated with Francois Riche and others. This work has now been folded in D4. 2000-05-004: Andrew Josey to forward the revised documents (the long scope and PAR) to PASC PMC (and to Austin Group) CLOSED: this was done on May 31st. The PAR was reviewed at the July PASC meeting and has been submitted to NesCom. 2000-05-005: Chair to call for comments on the errno man page wrt shading CLOSED: mail was sent to the reflector on June 12 2000-05-006: Ulrich Drepper to submit aardvark for the additional error returns for these functions (maths funcs), using the C99 text as a basis. CLOSED: We need further discussion and directions to see whether all implementations will support IEC 60559, the chair will circulate a note to the group regarding this post D4. 2000-05-007: Ulrich to submit proposal on how to use restrict. CLOSED -- see AUSTIN/45, submitted 5/16/00, final update circulated as AUSTIN/45r1, 12 June. 2000-05-008: Yvette and Cathy to confer on XBDd3 ERN #15 CLOSED -- the editorial feeling was that is that the codes should stay separate from the conformance requirements, as they are part of the global notations and contain more than just options- this is now covered further in XRAT. 2000-05-009: Mark Brown to set up conf call involving Donn Terry and Gary Miller at least to discuss XBDd3 ERN 83 - ERN 85. CLOSED: The conference call took place. 2000-05-010: Ulrich Drepper (in conjunction with Gary Miller) to submit Aardvark addressing XBDd3 ERN 121 proposing a new API to solve this problem, plus a definition of collation sequence. CLOSED: no new API, no new definition 2000-05-011: Frank Prindle to file interp request for XBDd3 ERN 163 CLOSED: see PASC 1003.1-109 2000-05-012: Andrew Josey to raise corrigenda against XNS5v2 for netdb.h (XBDd3 ERN 166) CLOSED: This is done and will be forwarded to the Open Group's June meeting of the Platform Pillar Executive Board. 2000-05-013: Andrew Gollan to investigate getip*() as to their future. (XBDd3 ERN 166) CLOSED in this meeting, they are stricken from the draft 2000-05-014: Andrew Josey to file interp against .1d (XBDd3 ERN 179). Add editors note with problem statement and probable resolution as given here CLOSED: pasc-1003.1-108 2000-05-015: Donn Terry (XSHd3 ERN 20) to file interp request against .1 for this. CLOSED. 2000-05-016: Donn Terry (XSHd3 ERN 32) to file interpretation against .1j to see what is right answer. The reviewers did not believe that it was ambiguous. CLOSED. 2000-05-017: Nick Stoughton (XSHd3 ERN 37) to propose suitable aardvark for actual additions. OPEN: unless text is supplied and agreed, this will be closed post D4 and we will document that Raw Sockets are not addressed in this standard. (I had previously looked for suitable text in 1g and not found any). 2000-05-018: TOG OR (XSHd3 ERN 82) to investigate outcome of previous discussion on bsd_signal CLOSED: The Base WG recommends that bsd_signal() be marked Obsolescent. 2000-05-019: Andrew Gollan to investigate XSHd3 ERN 175 (STREAMS fattach) and propose a response OPEN: a revnote will be added in D4 2000-05-020: Andrew Josey to investigate (XSHd3 ERN 256) where this came from (This "7858" was also in XSH Issue 5. I do not have Issue 4 or earlier with me, further investigation needed, we could just strike the wording in parentheses.) CLOSED: the 7858 has been removed. 2000-05-021: Al Simons (XSHd3 ERN 294) to provide additional words for example. CLOSED: Example to insert at XSHd3 line 15264, replacing current example: #include #include ... gid_t *group; int ngroups; long int ngroups_max; ngroups_max = sysconf(_SC_NGROUPS_MAX); group = (gid_t*)malloc(ngroups_max * sizeof(gid_t)); ngroups = getgroups(ngroups_max, group); 2000-05-022: Andrew Gollan (XSHd3 ERN 296) to forward socklen_t info to IETF WG for inclusion in RFC 2553 replacement (IPv6 API) when published CLOSED 2000-05-023: Donn Terry (XSHd3 ERN 301) to file interp against .1 for this. CLOSED. 2000-05-024: Andrew Gollan (XSHd3 ERN 330) to provide more detailed editing instructions to the editor. CLOSED 2000-05-025: Don Cragun (XSHd3 ERN 394) to check if Sun have an example of makecontext CLOSED: no suitable example is available. A reviewers note will be added requesting an example. 2000-05-026: Donn Terry (XSHd3 ERN 408) to file an interpretation request against .1 1996 for this. CLOSED 2000-05-027: Andrew Josey (XSHd3 ERN 426) to consider moving rationale around when handling XRAT at D4 CLOSED 2000-05-028: Editor (XSHd3 ERN 442) to include long example by inclusion in XRAT CLOSED: the section of text has been located and is ready to go into the XRAT volume. 2000-05-029: David Butenhof (XSHd3 ERN 465) to provide detailed edit instructions CLOSED: page 966, paragraph at line 29548 Both pthread_getspecific() and pthread_setspecific() may be called from a thread-specific data destructor function. A call to pthread_getspecific() for the thread-specific data key being destroyed will return the value NULL, unless the value is changed (after the destructor starts) by a call to pthread_setspecific(). Calling pthread_setspecific() from a thread-specific data destructor routine may result either in lost storage (after at least PTHREAD_DESTRUCTOR_ITERATIONS) or an infinite loop. 2000-05-030: Donn Terry (XSHd3 ERN 472) to submit interp. against .1 1996. CLOSED 2000-05-031: Andrew Josey (XSHd3 ERN 472) to investigate EPERM in pthread_mutex_init() and pthread_rwlock_init(), and to delete if not implemented anywhere. CLOSED. There are type A test assertions for these, so it does appear to be implemented. 2000-05-032: Frank Prindle (XSHd3 ERN 483) to submit more detailed edit instructions CLOSED: These were submitted and reviewed by the Base WG, and the set of changes actioned. 2000-05-033: Donn Terry (XSHd3 ERN 506) to rewrite rationale from .1 1990 and resubmit if appropriate CLOSED, see below. @ Page 1143 Line 34757 Section seekdir Objection [] In response to AI 2000-05-033, insert the following text: The seekdir() and telldir() functions were originally proposed for inclusion in earlier revisions but were excluded because they are inherently unreliable when all the possible conforming implementations of the rest of the standard were considered. The problem is that returning to a given point in a directory is quite difficult to describe formally, in spite of its intuitive appeal, when systems that use B-trees, hashing functions, or other similar mechanisms to order their directories were considered. Even the simple goal of attempting to visit each directory entry that is unmodified between the opendir() and closedir() calls exactly once is difficult to implement reliably in the face of directory compaction and reorganization. Since the primary need for seekdir() and telldir() is to implement file tree walks, and since such functions have since been added, and since in that more constrained context the goal of visiting unmodified nodes exactly once has been achieved, and since they constrain future implementations, there seems to be no reason to include these functions in the POSIX standard. I don't feel competent to rationalize their inclusion in XSI, as I can't rationalize it on any grounds but "tradition". That will have to be someone else's problem. Personally, I believe that including them works against the long-term betterment of the technology, because the DO cripple the options for better directory structures. If/when we resolve the "don't use this in new applications" flag, these certainly should be marked that way, and if they cannot be eliminated, I'd prefer to see them at least marked obsolesent. Editors Note: although Donn supplied wording, given subsequent discussions on the list, and the fact that these XSI functions are present and the fact that the CR was rejected we could not take these words "as is" - This was also discussed here at the October plenary (see section 11). 2000-05-034: Ulrich to propose suitable words for XSHd3 ERN 573 CLOSED - see mail seq 1141 2000-05-035: TOG OR (XSHd3 ERN 616) to raise interp request against SUSv2 XSH5 to whether it can be ruled that truncate will increase files (contradiction between 43538 and 43540 in XSH D3). CLOSED: The Base WG agreed that it can increase the file sizes. 2000-05-036: Frank Prindle (XSHd3 ERN 622) to identify list of all XSI functions that need to have ELOOP added (and the location in text) CLOSED: Frank submitted the changes and they have been actioned, note that ELOOP fix to XNS function-4 line 36089 was changed to 36108. 2000-05-037: Ulrich (XSHd3 ERN 652) to supply wording for app usage CLOSED 2000-05-038: TOG OR to forward XSHd3 ERN 676 to OGTGBASE for consideration CLOSED: the request has been forwarded 2000-05-039: Andrew Josey (XCUd3 ERN 6) to propose new words and mail to meeting attendees CLOSED: see the XCUd3 change request report 2000-05-040: TOG OR to forward XCUd3 ERN 44 to OGTGBASE for consideration CLOSED: this has been forwarded 2000-05-041: Andrew Josey (XCUd3 ERN 45) to check shallification of SCCS utils CLOSED. This has been done in D4. 2000-05-042: TOG OR to forward XCUd3 ERN 68 (compress)to OGTGBASE CLOSED : this has been forwarded. 2000-05-043 Yvette to confer with IEEE lawyers about patents (re: XCUd3 ERN68) CLOSED: IEEE requires a letter from Unisys even though the patent is disputed, or the description reworded to avoid it. We will reword the text. 2000-05-044: Andrew Josey (XCUd3 ERN 89) to mirror bekerly.edu copy at opengroup.org CLOSED. The files are now mirrored on an Open Group ftp site 2000-05-045: TOG OR to refer XCUd3 ERN 122 to OGTGBase for consideration CLOSED: this has been forwarded 2000-05-046: AJ to check against .2d for guidance on XCUd3 ERN 187 CLOSED: Yes we should accept this CR, that this should be a single comma. 2000-05-47: AJ to check on XCUd3 ERN 188 CLOSED: There does not appear to be any normative text in .2d to support this. 2. Procedures Update The JDOCS procedures have been formally adopted by all three member organizations. 2.1 Issues List New issues added: ISSUE 11. Leap seconds and how to handle them. ISSUE 12. Range expressions in locales. 2.2 Consent List No changes. 3. Identification of ORs and Chair Election PASC - Don Cragun. WG15 - Nick Stoughton. TOG - Mark Brown. 4. Status Reports 4.1 Austin Group Status Andrew Josey gave a brief overview of the mission and purpose of the Austin Group as an introduction for the new members. Currently 360 participants from a wide mix of interest groups. Draft 1 published June 1999. (2500 pages) Draft 2 published October 1999. (2700 pages) Draft 3 published February 2000. (3196 pages) Draft 4 published August 2000 (3590 pages) Joint Memorandum of Understanding (MoU) signed between IEEE and TOG to cover copyright. A substantial amount of time has been devoted so far to this standard, and this continues to rise. Many people worked around the clock for several weeks to produce and ballot on D4. Before publication, electronic access to the documents is permitted, but this will be removed at publication. D4 went through concurrent formal ballots in ISO and IEEE (plus Austin Group itself). IEEE ballot period closed with 85% return, 69% affirmative. From this draft onward, we will use pro-forma aardvark responses to speed up the process. R1.Reject: The requirement is from a base document and to change it is out of scope. Bringing it in scope would require an interpretation, corrigenda or resolution from the appropriate body. R2. Reject: this interface is not a candidate for Legacy, the list of Legacy interfaces was considered in March 1999 and is now final. It is widely used in historic practise and deprecating this interface would break the contract with the application developer. R3. Reject: we cannot see the problem at the referenced lines, as such this comment is non-responsive. R4: Reject: no action is specified in the aardvark comment. R5: Reject; The review team disagrees with the problem statement because.. ... {further rationale needed} R6: Reject: The review team believes that accepting the proposed change would decrease consensus. R7: Reject; this is out of scope. 4.2 PASC/POSIX Status .1q approved (Tracing) .1a and .2b continue to languish, but need very little effort to complete. 4.3 IEEE/TOG Status TOG: JDOCS procedures approved. Corrigenda approved. IEEE: JDOCS procedures approved. 4.4 ISO Status JDOCS Procedures approved. The concurrent CD registration and final CD ballot is in progress and closes at the end of December (ballot on D4). 4.5 C99 Status C99 is a formally approved international standard. Defect reports are now being addressed. ACTION: AJ to talk to John Benito to ensure all defect resolutions are incorporated. ISSUE: how to handle c99 defect reports (where Austin Group incorporates fixes, but base doc does not). 4.6 Networking Status An update to RFC8233 is in progress, we hope to encourage them to adopt the same interface prototypes as in the current draft. 4.7 JPC Status No report. 5. Old Business Document Layout/Style Donn Terry commented on the use of fonts, and why they differ from original POSIX. ACTION Donn Terry and Don Cragun to consider this. The document should remain self indexing, but there may be issues regarding white space. Line numbers should remain. 6. New Business 6.13 Aardvark Review Aardvark discussions are captured in the aardvark itself, and not further minuted. Only issues and actions arising from these discussions are noted below. 6.13.1 XBD Aardvark 409 comments Only noted here are those ERNs that were discussed. Other had pre-disposed comments that were not argued during the meeting. XBD ERN 16: Reject: Various identifiers exist on every page (including the running header and footer) to help work oput where you are. The editors will discuss this with the submitter. XBD ERN 17: Dup - This was covered by taking the individual comments. XBD ERN 19: Reject. Out of scope. Possibly detrimental to embedded systems. This is really a profile issue. This is a solution to something that has never previously been stated as a problem. XBD ERN 25: This was discussed in the workplan discussion. Some revised sections will be circulated in this way (maths and printf functions). See later minutes for the full disposition. XBD ERN 28: AAM Leave the current wording as is for now (done by strings). We expect WG15 to action this in their comments against the draft and will change the strings at that time. XBD ERN 32: AAM: remove normative refs from frontmatter (xxiv) and add pointer to normative text version of normative refs. ACTION Yvette to check placement of references. XBD ERN 43: AAM, use codes MC1 and MC2, and add these to the codes section (1.5) XBD ERN 49: Accept (ACTION TOG OR to request OGTGBase discuss this and provide a resolution permitting the dropping of these functions) XBD ERN 51: AAM, "Due to export restrictions on the decoding algorithm in some countries, implementations may be..." XBD ERN 52: defer (Nick/Andrew) ** XBD ERN 67: AAM - delete the term at 3.22 XBD ERN 81: AAM - used "Range Expressions within Regular Expressions" XBD ERN 83: defer I18N Revisited with Gary Miller: Reject. After considerable discussion, R6 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 86: AAM "A locale specific method for counting and displaying years" XBD ERN 93: AAM "A period of time ..." XBD ERN 94: AAM Change the term to be "Memory Mapped Files" (only) "A facility to allow applications to access files as part of the address space." XBD ERN 95: AAM The terms are all defined elsewhere, so just add xrefs. XBD ERN 102: Accept XBD ERN 112: AAM - change rationale. ACTION Glen Seeds to provide rationale explaining why the POSIX clock is the way it is and what is the consequence of this. CLOSED (rationale included in DTs action below) ACTION Donn Terry to rephrase definition sentence "Whether and how ...", line 3495) 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. XBD ERN 113: defer to editors (this is aesthetics only, the text has always had these large constants, and so should probably stay that way) XBD ERN 114: Accept XBD ERN 115: Accept XBD ERN 116: defer I18N Revisited with Gary Miller: ACTION Donn Terry to file a defect report on this with WG14 XBD ERN 117: defer I18N Revisited with Gary Miller: AAM - no change. Answer is "Because it is in C99". See 6.2.5, para 3 XBD ERN 124: AAM Add p 135, line 3811 "Characters defined in Table 6-2 on p xx may also be used in character set description files." DEFER for I18N and keld (l3805) Revisited ... all OK with proposal above. XBD ERN 125: Accept XBD ERN 126: DUP 127 XBD ERN 127: defer I18N (and Keld) Revisited with Gary Miller: Reject - this is in ISO C and the only addition we are making is naming the null character NUL. This is allowable. XBD ERN 128: Reject: this is our definition, not inherited from C. Therefore the extension above and beyond C's requirements does not need to be called out. XBD ERN 129: defer Keld and I18N Revisited with Gary Miller: Accept XBD ERN 130: AAM - add "except as noted below" to end of first sentence. defer I18N Revisited with Gary Miller: AAM as shown above is correct. XBD ERN 133: defer I18N Reject - following from 135. XBD ERN 134: defer I18N Revisited with Gary Miller: Straw poll taken - for 2, against 5. Reject - R6 XBD ERN 135: defer I18N Revisited with Gary Miller: Extremely long and wordy debate on repertoiremaps. Call for Straw poll on whether this is worth continuing: No. R5 (and probably R7) XBD ERN 139: accept XBD ERN 143: AAM - shallification pass 42. AJ will rework this section and change the "cans" to shall's as per .2 p147-150 XBD ERN 146: Accept XBD ERN 147: Reject - withdrawn by objector. XBD ERN 150: Accept XBD ERN 151: DEFER: The term "cannot" was discussed at the previous meeting, with Yvette Ho Sang present, and it was believed then that no action was required. ACTION Yvette to confirm that this term (cannot) is acceptable. XBD ERN 154: defer Keld I18N DUP 83 XBD ERN 155: AAM - ACTION AJ to reword introuction to 7.3.5.2 to show that the entire section is XSI. Move all examples in chapter 7 to XRAT so chap 7 more aligned with original .2. Change 5266 table header last col to "Conversion Specifier/Modifier" XBD ERN 156: Lengthy discussion on environment variables starting with digits. All in general agreement that these are a bad idea, but are legal in some contexts. ACTION Glen Seeds to propose new wording to cover this problem. CLOSED: Use: at line 5908-5910, append to end of sentence "and shall not begin with a digit." After 5915, add note: "Other applications may also have difficulty dealing with environment variable names that start with a digit. For this reason use of such names is not recommended anywhere." After 1883 in XRAT add: "In addition to the obvious conflict with the shell syntax for positional parameter substitution, some historical applications including some shells exclude names with leading digits from the environment." XBD ERN 157: AAM "Users should not set the NLSPATH variable unless they have a specific reason to override the default system path. Setting NLSPATH to override the default system path produces undefined results in the standard utilities and in applications with appropriate privileges." XBD ERN 158: defer I18N Revisited with Gary Miller: Another long discussion on the meaning of the question. Reject - R5. The local categories cannot be made to be independent. XBD ERN 165: defer I18N DUP/AAM see 83 XBD ERN 167: defer I18N Revisited with Gary Miller: Accept XBD ERN 169: defer I18N Revisited with Gary Miller: Accept XBD ERN 177: AAM delete functions "inet_lnaof(), inet_makeaddr(), inet_netof(), inet_network()". we'll also need to remove these pages from XSH XBD ERN 178: Accept XBD ERN 179: Accept XBD ERN 180: Accept XBD ERN 181: Accept XBD ERN 183: DUP 182 XBD ERN 188: Accept (shallification) XBD ERN 189: Accept XBD ERN 190: Accept XBD ERN 192: Accept XBD ERN 193: AAM. Correct typo. Editors have notes for restructuring to we have the text followed by the constants in blocks XBD ERN 194: Accept XBD ERN 196: AAM - do as suggested, and add to change history that Technical Corrigendum XXX was applied. XBD ERN 197:Accept XBD ERN 200: A XBD ERN 202: AAM, OB shade 8623 (and remove LEGACY), Change the description for FNM_NOSYS to "Reserved", check CH. XBD ERN 203: AAM see also 202, mark as OB, fix CH, mark reserved. XBD ERN 204: Accept +++++++++++++++++++++++BREAK 5.30 pm++++++++++++++++++++++++++++++++ XBD ERN 205: Accept XBD ERN 206: Considerable discussion on 8-bit architecture. If we mandate int8_t then non-8 bit architectures will have to have very smart compilers. However int8 (and friends) are required by the new mandatory networking interfaces. There is knock-on impact to I18N (Unicode systems might want 16 bit bytes). AAM - remove from inttypes, strengthen stdint.h to make these types mandatory, add reviewers note on consequences of this. Replace 11776 - 11777, with modelled on 11785-11794 without the "least". ACTION Andrew Gollan to provide rationale on making these types mandatory (note also that C99 requires 8 bit bytes!) XBD ERN 207:AAM move 8845-8857 to after text added in ERN 206 (stdint.h) XBD ERN 209: Reject - conflicts with 208. XBD ERN 211: DUP 212 XBD ERN 212: AAM (check that all headers called out in 211 are covered by DWC objections) stdarg.h,stdbool.h,stddef.h,stdint.h,tgmath.h XBD ERN 213: Accept XBD ERN 214: Accept XBD ERN 215: Accept XBD ERN 217: Accept XBD ERN 218: Add reviewers note anticipating a corrigenda XBD ERN 220: AAM - spell it out XBD ERN 222: Accept XBD ERN 223: ignore, this is part of 224 XBD ERN 224: DUP 222 XBD ERN 225: Accept XBD ERN 229: Accept XBD ERN 230: Accept XBD ERN 231: Accept XBD ERN 232: AAM - marker is XSI not TSA. Add reviewrs note to point out Interp 101. ACTION AJ to encourage interp group to finalize 101. XBD ERN 235: Accept Add general reviewers note make sure that all macros are called out as macros. ACTION Andrew Gollan to provide a definition of symbolic names/macros etc. XBD ERN 237: substantial discussion on this. Reject, use %j modifier. There is already substantial contrary existing practice. This restriction was previously lifted (by LFS). Apps that assume 32 bit architectures are already broken in the presence of 64 bit ones. XBD ERN 238: AAM, use the boilerplate for where there are changes on the page(there will be after this round of rdvk is applied) XBD ERN 239: Accept XBD ERN 240: AAM - add NOTE to end of section to the effect that applications can test for optional types here by using the corresponding limit macro. Make intptr_t and uintptr_t XSI shaded and mandatory. XBD ERN 243: AAM add reviewers note anticipating Tech Corrigenda from WG14. XBD ERN 244: defer for WG14 TC. ((discussed adding new definitions "Decimal, Octal or Hexadecimal Constant" (as defined by Clive) and "Integer Constant" as "D/O/H constant with optinal suffix" XBD ERN 245: DUP 244 XBD ERN 246: AAM - remove braces. 11983- 11985 should be in Roman, not italic. XBD ERN 247: AAM - use ed recommendation, but without {} XBD ERN 250: Considered. AAM - Add "is defined as a macro" at 12843 XBD ERN 252: AAM use "following" XBD ERN 254: Reject: S_IFSOCK is required for isfdtype() (from 1003.1g). ACTION Nick Stoughton to propose scope extension for isfdtype() for other file types. XBD ERN 255: R6. Add to future directions "No new S_IFMT symbolic names for the file type values of mode_t will be defined by this standard; if new file types are required, they will only be testable through S_ISxx() macros instead." XBD ERN 256: Reject - this is a quality of implementation issue. Why make a conformance distinction based on this? XBD ERN 259: AAM - see ed recommendation) XBD ERN 262: DUP 263; AAM - add this rationale. (note first bit covered by 263) XBD ERN 263: Accept XBD ERN 265: Reject until WG14 TC forthcoming XBD ERN 267: Accept XBD ERN 268: R7 <<<<<< XBD ERN 269: AAM - make XSI (part 2 of the Ed recommendation) XBD ERN 271: AAM - this is actually a change in XCU; change ps command so as to use units of 1024 bytes (as in 1003.2). Also mailx use 100_000 bytes in app usage, page 2814, linbe 23183. (also checked megabyte usage, all is OK). XBD ERN 272: AAM - Andrew has notes. REVIEWERS NOTES: Page 123 now fulfilled, and can be removed. Page 167 can go. ACTION Ulrich Drepper/Fred Tydeman to propose suitable equations for float.h Page 273 can go Page 287 change limits.h to separate out XSI and non-XSI limits; XSI has the bigger numbers (255 and 1024). Change Page 285, lines 9278-9283 Page 515, add to namespace table for ANY header the prefix _XOPEN_ (not XSI shaded). Add new limits _XOPEN_NAME_MAX (val 255) and _XOPEN_PATH_MAX (val 1024) and use these in the limits NAME_MAX and PATH_MAX. Page 288 change the non _POSIX_ limits to use the _POSIX_ values (e.g. NGROUPS_MAX is defined in terms of _POSIX_NGROUPS_MAX), and increase the size of the _POSIX_ limits as suggested in the rev. note. Remove the rev note. Page 306 ... the interp is finalized, fix the problem as noted. (also note page 1313 needs to be ssize_t) --------------------------------------------------------------------------------- 6.13.2 XCU Aardvark XCU ERN 1: Lengthy discussion, trying to understand the problem. AAM, remove line 5960 on p189 of XBD. Line 5962 change "shall" to "can". After 5965 add: "The use of the I18N variables by utilities described in the Shell and Utilities vol of this std are described in the environment variables section for those utilities." XCU ERN 3: AAM, also add reviewers note to point 5 asking for "Can we do better with other file type combinations". XCU ERN 4: AAM, change "8" to "eight" (there is already a defn), and change XSI to MAN. XCU ERN 20: R6 XCU ERN 34: see 36 XCU ERN 36: ISSUE: In the light of this comment, the ORs would like to reconsider the inclusion of #! (TOG in particular). Return to explicitly unspecified what happens with #!. OR FORMAL VOTE - WG15 keep, TOG remove, IEEE remove. Donn Terry observed that #! is a very useful tool, and although the current implementations are not suitable for standardization, that he would very much like to see a version that was suitable proposed for standardization in the future. He encouraged implementation development in that area. XCU ERN 46: AAM - Add reviewers note to ask for input. ACTION Nick Stoughton to request Usenix gurus for input on this grammar. XCU ERN 47: Accept XCU ERN 48: Defer/AAM - ACTION Don Cragun to provide specific words for TZ usage XCU ERN 49: Defer/AAM - ACTION Donn Terry to file an interp against .2b requesting clarification (ar utility), and to propose changes. XCU ERN 58: Accept XCU ERN 102: AAM, copy lines from 17737-17742 XCU ERN 103: AAM - no change required here, silence DOES mean that output is prohibited. Also add "completely" to sentence on page 2227, line 878 ("... completely describes the standard output ..."). Similarly for OUTPUT FILE, line 919, add "completely" ("...completely describes ...") Also add reviewers notes here (p 2227) asking everyone to check the stdout/output files section of every command/utility. XCU ERN 104: AAM - use "chgrp utility" instead of "it". XCU ERN 105: AAM - page 3336 line 1022 change first word "All" to "Most". XCU ERN 106: Reject. R5. All the statements requested to be added are already present in introductory sections. XCU ERN 107: AAM - change "it" to "the chown utility" XCU ERN 112: Accept XCU ERN 142: AAM - remove the "(binary 001)" and add <> around SOH and add POSIX locale (" in the POSIX locale"). Equivalent cleanup required in the admin utility. XCU ERN 145: Accept XCU ERN 185: AAM - use option 1 (i.e. we confirmed it is -s). ACTION Donn Terry to provide detailed changes required. XCU ERN 186: Accept XCU ERN 266: Accept (no change required) XCU ERN 267: Accept, delete lisp support (lisp edits supplied by DT) XCU ERN 314: R6 XCU ERN 330: AAM - add a line in rationale to explain existing practice. "The definition of the fuser utility follows existing practise" XCU ERN 340: Accept XCU ERN 352: Accept XCU ERN 353: Accept XCU ERN 355: Accept XCU ERN 356: Accept XCU ERN 369: Accept XCU ERN 370: Accept XCU ERN 373: Accept XCU ERN 374: Accept XCU ERN 375: Accept XCU ERN 378: Accept +++++++++++++++++++++++++++++++++++++++ break 5.40 pm Wed ++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++ resume 8:00 am Thurs +++++++++++++++ XCU ERN 384: Accept XCU ERN 385: defer I18N Reject see XBD 135 XCU ERN 409: AAM - use option 1 with additional changes , change "unspecified" to "implementation-defined", change "copy" to instance. Add at 23650 "The result of setting MAKEFLAGS in the Makefile is unspecified." XCU ERN 417: agreed the para needs rework, defer - ACTION TOG OR. XCU ERN 443: AAM - reformatted Don's words (Glen Seeds provided text) (was file od.txt) XCU ERN 444: AAM - Long discussion on what how and where to fix. Change "1,2, and 4" to "1,2,4 and 8" on line 26112 Aslo add "The implementation shall support the decimal value corresponding to the C-Language type long long" to p2891 l26113 after sizes Add revnote: D4 XCU444 We have addressed long long but not chosen a symbolic name for it, do we need to invent a new character notation for long long? XCU ERN 445: Accept XCU ERN 446: Accept XCU ERN 478: defer ACTION Donn Terry to propose specific changes XCU ERN 480: - defer I18N ACTION Glen Seeds to reword. XCU ERN 518: AAM - delete 31469-31470 reference to -W. Restore "The -W (capital-W) option shall be reserved for vendor options" to XBD l 7520 p 229. XCU ERN 523: AAM (use s rather than characters) XCU ERN 554: Accept XCU ERN 570: Accept XCU ERN 572: AAM - fix the rationale. Delete first and third bullet from rationale. ACTION Donn Terry to provide additional paragraph explaining why these two features are XSI only. XCU ERN 578: AAM - ACTION Donn Terry to supply new rationale with XSI taken into account XCU ERN 579: Accept XCU ERN 600: defer to ACTION TOG OR to request OGTGBase to fix this. XCU ERN 601: Accept XCU ERN 602: Accept XCU ERN 605: AAM - take the change as noted, also swap items 2 and 3 in the numbered list XCU ERN 610: Accept XCU ERN 615: Accept XCU ERN 619: Accept XCU ERN 620: Accept XCU ERN 621: Accept XCU ERN 626: defer - ACTION Donn Terry to propose more detailed changes for vi and more re logical v physical lines. XCU ERN 635: Accept XCU ERN 636: Accept XCU ERN 637: Accept XCU ERN 639: Accept XCU ERN 640: Accept XCU ERN 641: Accept XCU ERN 642: Accept XCU ERN 643: Accept XCU ERN 646: R7 - ACTION Donn Terry to discuss this with Keith Bostic and file interp if needed. XCU ERN 654: Accept XCU ERN 655: Accept XCU ERN 656: Accept XCU ERN 657: Accept XCU ERN 658: Accept XCU ERN 659: Accept XCU ERN 660: Accept XCU ERN 662: Accept XCU ERN 679: AAM - ACTION DT to file interp request agaisnt .2b for clarification - remove revnote XCU ERN 687: Accept XCU ERN 688: Accept XCU ERN 689: Accept XCU ERN 690: Accept XCU ERN 691: Accept XCU ERN 693: Accept XCU ERN 701: Accept XCU ERN 702: Accept XCU ERN 703: Accept XCU ERN 712: Accept XCU ERN 720: Accept XCU ERN 721: Accept XCU ERN 722: AAM - use second choice XCU ERN 728: Accept XCU ERN 733: Accept XCU ERN 735: Accept XCU ERN 737: AAM - restore CW for 40977 to 41019 change extended headings to code fragments. Also sample output on p 3292 l 41477-41489 should be CW XCU ERN 738: Accept XCU ERN 739: Accept Reviewers Notes: A pass through the reviewers notes in XCU was made, with actions assigned appropriately. Andrew has some marked up changes resulting from this. An ISSUE with stat and large files was noted in respect of ftw(). 6.13.3 XSH Aardvark XSH ERN 2: Accept XSH ERN 4: AAM - just ualarm and usleep marked as OB. XSH ERN 5: AAM, add With each function or header from the C standard, a statement to the effect that "any conflict is unintentional" is included. That is intended to refer to a direct conflict. This standard acts in part as a profile of the C standard, and it may choose to further constrain behaviors allowed to vary by the C standard. Such limitations are not considered conflicts. XSH ERN 12: Accept XSH ERN 14: AAM - add description of size_t to regex.h in XBD. XSH ERN 16: Accept (also l 8146 p249 if XBD) XSH ERN 31: Defer - ACTION Andrew Josey to check if an interpretation has been filed, and what is it status. XSH ERN 32: Defer (accept in principle) - ACTION TOG OR to refer to OGTGBase XSH ERN 33: AAM Insert after the end of the sentence on 1878: Since there is no way for a strictly conforming application to determine if this relaxation applies, all strictly conforming applications which rely on ordering of output shall be written in such a way hat will operate correctly if the relaxation applies. XSH ERN 34: Accept XSH ERN 42: Accept XSH ERN 44: Defer - ACTION Frank Prindle to resubmit lost interp. Add reviewers note explaining the anticipated action. XSH ERN 47: Accept XSH ERN 48: DUP 4 XSH ERN 49: Reject - these interfaces have been internationalized for 10-12 years, and do not need to revert at this point. XSH ERN 50: Accept - CX shading to end of para. XSH ERN 53: AAM- Fred Tydeman discussed C method of handling NaN and EDOM. This appears to be substantially different to the method currently in XSH. For example, it is possible to set the math library to not use errno (via the flag math_errhanndling). Change XBD page 81 l 2369-2370: "A value ..." --> "A set of values that may be stored in a floating type but are neither inf nor valid floating point numbers. Not all systems support NaN values." Also change XBD page 74 line 227-2228 "A value representing plus infintiy or a value representing minus infinty, that can be stored in a floating type ..." and pluralize last word (value -> values). For all the places where EDOM is currently used, it should say "a domain error occurs." Similarly ERANGE -> a range error. General desire to preserve the same error handling options from c99. Line 4005 "If x is NaN, the asinh() ... shall return a NaN." Add new general concepts "Domain Error" and "Range Error" based on C99 7.12.1 paras 2 & 3: [start of new general concept] 4.x Treatment of error conditions for maths functions The following error conditions are defined for all functions in the header. 4.x.1 Domain Error A domain error shall occur if an input argument is outside the domain over which the mathematical function is defined. The description of each function lists any required domain errors; an implementation may define additional domain errors, provided that such errors are consistent with the mathematical definition of the function. On a domain error, the function returns an implementation-defined value; if the integer expression math_errhandling & MATH_ERRNO is nonzero, the integer expression errno acquires the value EDOM; if the integer expression math_errhandling & MATH_ERREXCEPT is nonzero, the ''invalid'' floating-point exception is raised. 4.x.2 Range Error A range error shall occur if the mathematical result of the function cannot be represented in an object of the specified type, due to extreme magnitude. [end of new general concept] [Also Add to ] The behavior of each of the functions in is specified for all representable values of its input arguments, except where stated otherwise. Each function shall execute as if it were a single operation without generating any externally visible exceptional conditions. [end of math.h addition] XSH ERN 54: Reject - OBE (withdrawn by submitter) XSH ERN 55: Defer - Action Mark Brown to file interp. Add reviewers note anticipating we will accept this ultimately. XSH ERN 62: Reject, we do not feel it appropriate to change the (admittedly bad) wording from C99. XSH ERN 63: Accept XSH ERN 64: Accept XSH ERN 65: Reject - overcome by math revisions. Withdrawn by objector. XSH ERN 66: DUP 53 XSH ERN 67: AAM, do action 1 only. App Usage becomes "None". XSH ERN 68: AAM - move 6315 - 6321 as indicated. 6314, add (XSI shaded) I_SVTX to list of bits. XSH ERN 69: Accept XSH ERN 72: AAM - use The message body is generated from the message and following arguments in the same manner as if these were arguments to printf(), except that the additional conversion specifier %m shall be recognized; it shall convert no arguments, shall cause the output of the error message string associated with the value of errno on entry to syslog() and may be mixed with argument specifications of the "%n$" form. If a complete conversion specification with the 'm' conversion character is not just "%m", the behavior is undefined. A trailing may be added if required. XSH ERN 75: AAM / DUP 53. Use recommendations resulting from 53. Do the specific action noted at the end of the rdvk (tiny source of conflict). XSH ERN 76: Reject - see 53. XSH ERN 77: DUP 4 XSH ERN 78: Accept XSH ERN 79: R7 XSH ERN 80: AAM - ACTION Donn Terry to provide other reorderings as promised. XSH ERN 81: Accept XSH ERN 82: DUP 81 XSH ERN 83: Accept XSH ERN 84: Accept XSH ERN 86: AAM - remove shading, add std c block and hope that 53 will fix the EDOM problems. XSH ERN 87: DUP 86 XSH ERN 89: Accept XSH ERN 90: R1 XSH ERN 93: Accept XSH ERN 98: Accept XSH ERN 99: dup 98 XSH ERN 103: defer ACTION TOG OR to ask OGTGBase for clarification XSH ERN 104: Reject - this is a result of a D3 aadvark. XSH ERN 106: Reject - both actions are distinct, both are needed, the wording is correct. XSH ERN 109: AAM - also need additions for c99 describing this change since c89. ACTION Ulrich Drepper to provide this change text XSH ERN 110: AAM XSH ERN 112: AAM XSH ERN 113: Reject see 53 XSH ERN 114: AAM XSH ERN 115: defer - ACTION TOG OR to ask OGTGBase how to get a file desc for this portably. XSH ERN 116: Reject see 53 XSH ERN 117: AAM see Ed recommendation --------------------------------- break at 6.30pm Thurs ---------------------- --------------------------------- resume at 8:50am Fri ---------------------- XSH ERN 118: Accept XSH ERN 119: Reject - R1 (this is ISO C wording) XSH ERN 120: Reject R5, not a hosted environment XSH ERN 121: Reject see 130 XSH ERN 122: Accept XSH ERN 123: Accept XSH ERN 124: Accept XSH ERN 125: Accept XSH ERN 126: DUP 126 XSH ERN 128: Reject - see 130 XSH ERN 129: Reject - see 130 XSH ERN 130: Accept XSH ERN 142: AAM (don't do the also bit at the end) XSH ERN 143: dup 142 XSH ERN 145: Accept XSH ERN 146: Accept XSH ERN 147: AAM - use a consistent font (editor's choice) (only in fprint/fwprintf/fscanf/fwscanfi and file format notation) ACTION Donn Terry to assist in locating all places where printf conversion characters are used and need alternate representation (font) XSH ERN 148: Accept XSH ERN 154: Accept XSH ERN 157: Accept XSH ERN 159: AAM (really reject, we are doing the opposite), descriptor is meant. Also add "descriptor" at line 14137 XSH ERN 160: Reject R5 not a problem. XSH ERN 162: defer until 53 resolved XSH ERN 163: considerable discussion. Reject - the inconsitency is intended, a portable app should not rely on this behavior, nor should they need it. XSH ERN 164: Reject - this would break existing applications. Also I18N problems XSH ERN 168: Accept XSH ERN 170: defer to OGTGBase XSH ERN 171: Accept XSH ERN 173: R7. If such an interface exists, please supply details. XSH ERN 175: Accept XSH ERN 178: Reject - See 179 / 130 XSH ERN 179: Accept see 130 XSH ERN 180: Accept XSH ERN 182: Accept (tho' its not needed) XSH ERN 185: AAM / defer ACTION Andrew Gollan to look at this XSH ERN 187: Accept XSH ERN 189: Accept XSH ERN 190: Accept XSH ERN 191: AAM - delete the functions XSH ERN 192: Reject, but remember the see-also actions from earlier. Lines 17159-17160 must be updated. XSH ERN 193: Accept XSH ERN 195: Accept XSH ERN 196: AAM - xref other functions XSH ERN 199: R5 - this is the only place this is discussed. XSH ERN 202: defer - ACTION Ulrich Drepper to check and make recommendation XSH ERN 203: defer - Ulrich to check XSH ERN 204: Accept XSH ERN 206: AAM - but drop GLOB_NOSYS in the suggested replacement XSH ERN 208: defer to OG TG Base XSH ERN 211: defer 53. XSH ERN 215: AAM - use "ISO-8859-1" in the action text XSH ERN 219: AAM - minor editorial change on p 1145 to separate out a para. The para on lines 20935-20937 constrains these functions suitably. XSH ERN 220: dup 219 XSH ERN 221: dup 219 XSH ERN 223: defer based on isfdtype issue initiated XSH ERN 224: Accept XSH ERN 226: Accept XSH ERN 228: AAM Andrew has notes XSI shade 22846, 22849-22850 The sign of.. XSH ERN 232: AAM - take first part (not issues regarding, as those are covered by 53) XSH ERN 233: reject 53 XSH ERN 234: Accept XSH ERN 236: dup 237 XSH ERN 237: AAM , take Ed recommendation, but not "also XSI shade lines 23870,23875" XSH ERN 238: Accept XSH ERN 239: defer - Action Frank Prindle. AAM - first change only XSH ERN 240: Accept XSH ERN 241: Accept XSH ERN 242: Accept XSH ERN 244: Accept XSH ERN 245: Reject - Ulrich says it is not needed XSH ERN 246: Accept XSH ERN 247: Reject 53 XSH ERN 249: AAM - remove "double-precision" on 27074, 27089, 27098. 27096, 27101 change nextafter to these functions. XSH ERN 251: Accept XSH ERN 254: defer - OGTGBase XSH ERN 256: dup 257 XSH ERN 257: Accept XSH ERN 258: R1 - ACTION Frank Prindle to file interp XSH ERN 259: dup of pointer page issue XSH ERN 260: Accept XSH ERN 261: Accept XSH ERN 263: Accept XSH ERN 264: Accept XSH ERN 265: Accept XSH ERN 266: Accept XSH ERN 268: defer ACTION Frank Prindle to ask the PASC realtime group XSH ERN 269: Accept XSH ERN 271: Accept XSH ERN 272: Dup 273 XSH ERN 273: Accept XSH ERN 274: defer ACTION Frank Prindle XSH ERN 275: Accept +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= OUT OF TIME +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= 48 further aardvarks with no predisposition. Volunteers from the plenary meeting will complete the dispositions and circulate at the end of next week. 7. Consent List The following items were agreed upon during this meeting and added to the Consent list (SD/2) AGREED to reverse our earlier decision, and abandon the #! proposal 8. Issues List The following new ISSUES arose during this meeting: ISSUE: How to deal with c99 defect reports and corrigenda; CX shade? Revision History? ISSUE: How to deal with shading for NaN. CX? XSI? Neither? ISSUE: Large files in ftw() ... ftw should walk the entire tree, but it also should fail if it encounters a large file with a 32 bit off_t (EOVERFLOW in stat). 9. Closing 9.1 Review of Action Items (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: 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. 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. 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. 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. 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. 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. qdel: Delete P2927, L29762. Delete P2979, L29764-29765. qhold: Delete P2982, L29889. Delete P2982, L29891-29892. qmove: Delete P2985, L29982. Delete P2985, L29984-2998 qmsg: Delete P2988, L30087. Delete P2988, L30089-30090. qrerun: Delete P2991, L30182. Delete P2991, L30184-30185. 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. qstat: Delete P3008, L30864. Delete P3008, L30867-30868. 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. uustat: Delete P3191, L37544. Delete P3191, L37546. 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 9.4 Document Register Note that Austin/SD1 (Issues list) and Austin/SD2 (Consent list) will be updated based on these minutes. AUSTIN/55 Andrew Josey Meeting agenda AUSTIN/56 Andrew Josey Austin Group Status October 2000 Slides AUSTIN/57 Nick Stoughton Minutes of the October 2000 meeting 10 Next Meeting(s) / Future plans Deadline for actions in mid-November Discussed staggering document releases (XBD ERN 25) ... problems arise from the fact that a number of edits jump around, global changes will go back and rechange some of the things already released, etc. Probably staggering will cause more problems that it will resolve. Wherever possible, particularly with hot topics and major changes, the editors will attempt to release early trial versions of sections for unofficial review. Next draft Dec 15 Next review Dec 15 - Feb 14 Next plenary meeting March 2001 (probably March 5-9) Plans from here: a. Maths functions. Firstly redo sample man pages for acos and acosh only and recirc. Once those are ok, then the Maths functions section to be redone and circulated for a 10 day review, followed by a teleconference of maths experts (at the call we will also consider the recommendations from Fred Tydeman). b. XRAT review XRAT review, the editors will predispose as many of the XRAT comments as possible, and then we will hold a separate teleconference to discuss any remaining open and any deemed controversial (timescale , 2-3 weeks time). c. Font usage in modifiers/specifiers in printf/scanf families Update one of the man pages below first and then recirc for review and feedback. Teleconference if necessary. fprintf/fwprintf/fscanf/wscanf families , the modifiers and conversion characters need to be cw on lists, and quoted as single chars inline. Redo file format notation. We need to circulate the changed pages for review, d. reviewing of sets of pages Review of sets of pages of incomplete edits? Is there a willingness to review sets of pages as we go along thru the edit cycle? For example, functions a-c, d-g, etc Reviewers would have to bear in mind that these will be work in progress items and that not all issues may have been addressed, but it would allow reviewers to see some pages prior to the complete draft being produced. If we have a page schedule are their volunteers? 11.AOB Range expressions (XBD D3 ERN 121) 2000-05-010 closed during aardvark review with Gary Miller 2000-05-019 re: XSH D3 ERN 175 fattach? 2000-05-033 re: XSH D3 ERN 506 seekdir rationale ACTION: Andrew Josey to work this rationale into seekdir. TO BE DONE NEXT TIME XSH reviewers notes, or via teleconference. The discussion on signals was postponed pending the outcome of the interpretation (posix .1 interp 117 , if finalized) This will come back to haunt us .... ! ADJOURN 1:29 Friday 13 Oct 2000