Anonymous | Login | 2024-12-04 05:25 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||||||||
0001873 | [1003.1(2024)/Issue8] Base Definitions and Headers | Editorial | Error | 2024-11-11 17:11 | 2024-11-14 17:20 | ||||||||
Reporter | geoffclare | View Status | public | ||||||||||
Assigned To | |||||||||||||
Priority | normal | Resolution | Accepted | ||||||||||
Status | Resolved | ||||||||||||
Name | Geoff Clare | ||||||||||||
Organization | The Open Group | ||||||||||||
User Reference | |||||||||||||
Section | (many) | ||||||||||||
Page Number | (many) | ||||||||||||
Line Number | (many) | ||||||||||||
Interp Status | --- | ||||||||||||
Final Accepted Text | |||||||||||||
Summary | 0001873: ISO editors Issue 8 comment 114 | ||||||||||||
Description |
In their comment 114 on Issue 8 the ISO editors requested that where we mention earlier versions of the standard, we specify which versions. The Austin Group's response was that a change would be considered for the next TC. My search for "earlier version" also turned up a few uses that aren't related to versions of the standard but I thought worth changing. |
||||||||||||
Desired Action |
On page 306 line 10796 section <math.h>, change:Earlier versions of this standard did not make this requirement, because they lacked the 'l' (lower case ell) versions of the constantsto: Versions of this standard earlier than Issue 8 did not make this requirement, because they lacked the 'l' (lower case ell) versions of the constants On page 341 line 11994 section <search.h>, change: Earlier versions of this standard explicitly used void for both node and key referencesto: Versions of this standard earlier than Issue 8 explicitly used void for both node and key references On page 415 line 14498 section <sys/stat.h>, change: For compatibility with earlier versions of this standard, the st_atime macro shall be defined with the value st_atim.tv_sec.to: For compatibility with versions of this standard earlier than Issue 7, the st_atime macro shall be defined with the value st_atim.tv_sec. On page 454 line 15850 section <time.h>, change: the former [0,61] seconds seen in earlier versions of this standard.to: the former [0,61] seconds seen in versions of this standard earlier than Issue 6. On page 558 line 19994 section 2.10.20.1 Addressing, change: IPv6 overcomes the addressing limitations of earlier versions by usingto: IPv6 overcomes the addressing limitations of IPv4 by using On page 658 line 23079 section basename(), and page 812 line 27814 section dirname(), change: Earlier versions of this standard seemed to allow thread-safe and non-thread-safe implementationsto: Versions of this standard earlier than Issue 8 seemed to allow thread-safe and non-thread-safe implementations On page 748 line 25818 section close(), change: Earlier versions of this standard left the state of fildes unspecifiedto: Versions of this standard earlier than Issue 8 left the state of fildes unspecified On page 812 line 27807 section dirname(), change: earlier versions of the standard did not mention whether elisionto: versions of this standard earlier than Issue 8 did not mention whether elision On page 1020 line 34951 section free(), change: However, earlier versions of this standard did not require thisto: However, versions of this standard earlier than Issue 8 did not require this On page 1107 line 38008 section getcwd(), change: In applications conforming to earlier versions of this standard, it was not possible to use the fchdir() approachto: In applications conforming to versions of this standard earlier than Issue 7, it was not possible to use the fchdir() approach On page 1121 line 38461 section getenv(), change: Some earlier versions of this standard did not require getenv() to be thread-safeto: Versions of this standard earlier than Issue 8 did not require getenv() to be thread-safe On page 1209 line 41298 section glob(), change: Earlier versions of this standard defined the behavior associated with the flag GLOB_MARK asto: Versions of this standard earlier than Issue 8 defined the behavior associated with the flag GLOB_MARK as On page 1237 line 42212 section in6addr_any, change: These variables were only described on the XBD <netinet/in.h> page in earlier versions of this standard.to: These variables were only described on the XBD <netinet/in.h> page in versions of this standard earlier than Issue 8. On page 1330 line 44719 section lgamma(), change: Earlier versions of this standard did not require lgamma(), lgammaf(), and lgammal() to be thread-safeto: Versions of this standard earlier than Issue 8 did not require lgamma(), lgammaf(), and lgammal() to be thread-safe On page 1335 line 44902 section link(), change: Earlier versions of this standard specified only the link() functionto: Versions of this standard earlier than Issue 7 specified only the link() function On page 1505 line 50501 section nftw(), change: Earlier versions of this standard did not make clear thatto: Versions of this standard earlier than Issue 8 did not make clear that On page 1554 line 52130 section popen(), change: Earlier versions of this standard required the command string to be passedto: Versions of this standard earlier than Issue 8 required the command string to be passed On page 1638 line 54681 section pselect(), change: In earlier versions of the Single UNIX Specification, the select() function wasto: In versions of The Open Group Base specifications earlier than Issue 6, the select() function was On page 1812 line 59958 section pthread_setcancelstate(), change: However, earlier versions of the standard did not permitto: However, versions of this standard earlier than Issue 8 did not permit On page 1856 line 61193 section read(), change: Earlier versions of this standard allowed two very different behaviorsto: Versions of this standard earlier than Issue 6 allowed two very different behaviors On page 2003 line 65810 section setregid((), and page 2009 line 65954 section setreuid((), change: Earlier versions of this standard did not specify whether the savedto: Versions of this standard earlier than Issue 7 did not specify whether the saved On page 2031 line 66622 section shmat(), change: applications written to earlier versions of this standard, whereto: applications written to versions of this standard earlier than Issue 8, where On page 2126 line 69445 section strerror(), change: Earlier versions of this standard did not explicitly require that the error message stringsto: Versions of this standard earlier than Issue 7 did not explicitly require that the error message strings On page 2141 line 70043 section strftime(), change: Some earlier version of this standard specified that applications wantingto: Versions of this standard earlier than Issue 7 specified that applications wanting On page 2173 line 71019 section strtod(), change: with the ISO/IEC 9899:1990 standard and thus earlier versions of this standard.to: with the ISO/IEC 9899:1990 standard and thus versions of this standard earlier than Issue 6. On page 2210 line 72254 section system(), change: Earlier versions of this standard did not require system() to be thread-safeto: Versions of this standard earlier than Issue 8 did not require system() to be thread-safe On page 2211 line 72272 section system(), change: Earlier versions of this standard required the command string to be passedto: Versions of this standard earlier than Issue 8 required the command string to be passed On page 2266 line 73916 section time(), change: Earlier versions of this standard allowed the width of time_t to be less than 64 bits.to: Versions of this standard earlier than Issue 8 allowed the width of time_t to be less than 64 bits. On page 2557 line 83453 section set, change: Earlier versions of this standard specified -h as a way to locate and remember utilitiesto: Versions of this standard earlier than Issue 8 specified -h as a way to locate and remember utilities On page 2636 line 86503 section awk, change: Earlier versions of this standard required implementations to support multiple adjacent <semicolon>sto: Versions of this standard earlier than Issue 7 TC2 required implementations to support multiple adjacent <semicolon>s On page 2684 line 88483 section cal, change: Earlier versions of this standard incorrectly required that the commandto: Versions of this standard earlier than Issue 7 TC1 incorrectly required that the command On page 2739 line 90542 section compress, change: Earlier versions of this standard limited the number of bitsto: Versions of this standard earlier than Issue 8 limited the number of bits On page 2739 line 90545 section compress, change: Earlier versions of this standard only supported LZW compression.to: Versions of this standard earlier than Issue 8 only supported LZW compression. On page 2746 line 90817 section cp, change: Earlier versions of this standard included support for the -r optionto: Versions of this standard earlier than Issue 7 included support for the -r option On page 2764 line 91503 section cut, change: Earlier versions of the cut utility worked in an environmentto: Historical versions of the cut utility worked in an environment On page 2785 line 92164 section dd, change: An earlier version of System V used block, but this has been updated in more recent releases.to: An early version of System V used block, but this was updated in later releases. On page 2802 line 92839 section diff, change: An earlier version of this standard specified the output format more preciselyto: Versions of this standard earlier than Issue 7 specified the output format more precisely On page 2805 line 92970 section dirname, change: because earlier versions of the standard did not permit elision of redundant <slash> charactersto: because versions of the standard earlier than Issue 8 did not permit elision of redundant <slash> characters On page 2828 line 93830 section ed, change: In earlier versions of this standard, an obsolescent - option was described.to: In versions of this standard earlier than Issue 6, an obsolescent - option was described. On page 2829 line 93879 section ed, and page 2910 line 97081 section ex, and page 2938 line 98098 section file, and page 3046 line 102109 section lex, and page 3233 line 109344 section od, and page 3364 line 114465 section sed, and page 3464 line 118264 section tr, change: Earlier versions of this standard allowed for implementations with bytes other than eight bitsto: Versions of this standard earlier than Issue 6 allowed for implementations with bytes other than eight bits On page 2830 line 93918 section ed, change: Earlier versions of this standard required address 0 for the c commandto: Versions of this standard earlier than Issue 8 required address 0 for the c command On page 2913 line 97217 section expand, change: Earlier versions of this standard allowed the following form in the SYNOPSISto: Versions of this standard earlier than Issue 6 allowed the following form in the SYNOPSIS On page 2950 line 98576 section find, change: and earlier versions of this standard only required support for -xdev.to: and versions of this standard earlier than Issue 8 only required support for -xdev. On page 2974 line 99422 section getconf, and page 2975 line 99445 section getconf, change: For compatibility with earlier versions,to: For compatibility with versions of this standard earlier than Issue 6, On page 3001 line 100427 section head, change: Earlier versions of this standard allowed a -number option.to: Versions of this standard earlier than Issue 6 allowed a -number option. On page 3030 line 101442 section join, change: Earlier versions of this standard allowed -j, -j1, -j2 options, andto: Versions of this standard earlier than Issue 6 allowed -j, -j1, -j2 options, and On page 3054 line 102406 section ln, change: Earlier versions of this standard did not specify these optionsto: Versions of this standard earlier than Issue 7 did not specify these options On page 3054 line 102417 section ln, change: Earlier versions of this standard were unclear in this case.to: Versions of this standard earlier than Issue 7 were unclear in this case. On page 3086 line 103648 section ls, change: Earlier versions of this standard did not describe the BSD -A optionto: Versions of this standard earlier than Issue 7 did not describe the BSD -A option On page 3087 line 103666 section ls, change: Earlier versions of this standard did not have the -k optionto: Versions of this standard earlier than Issue 7 did not have the -k option On page 3099 line 104154 section m4, change: Earlier versions of this standard allowed the exit status to beto: Versions of this standard earlier than Issue 8 allowed the exit status to be On page 3155 line 106428 section make, change: macro was not adopted in earlier versions of this standardto: macro was not adopted in versions of this standard earlier than Issue 8 On page 3157 line 106542 section make, change: Earlier versions of this standard defined comment linesto: Versions of this standard earlier than Issue 7 TC2 defined comment lines On page 3211 line 108544 section nice, change: Earlier versions of this standard allowed a -increment option.to: Versions of this standard earlier than Issue 6 allowed a -increment option. On page 3277 line 111138 section pax, change: Earlier versions of this standard did not specify any way to createto: Versions of this standard earlier than Issue 7 did not specify any way to create On page 3302 line 112165 section printf, change: Earlier versions of this standard specified that arguments for all conversionsto: Versions of this standard earlier than Issue 7 specified that arguments for all conversions On page 3318 line 112798 section pwd, change: An earlier version of this standard stated that the PWD environment variableto: Issue 6 of this standard stated that the PWD environment variable On page 3323 line 112995 section read, change: Earlier versions of this standard required the standard input to be a text fileto: Versions of this standard earlier than Issue 8 required the standard input to be a text file On page 3332 line 113323 section renice, change: Earlier versions of this standard allowed the following forms in the SYNOPSISto: Versions of this standard earlier than Issue 6 allowed the following forms in the SYNOPSIS On page 3382 line 115255 section sh, change: Earlier versions of this standard required that input files to the shell be text filesto: Versions of this standard earlier than Issue 8 required that input files to the shell be text files On page 3393 line 115656 section sort, change: Earlier versions of this standard allowed the -o option to appearto: Versions of this standard earlier than Issue 7 allowed the -o option to appear On page 3393 line 115660 section sort, change: Earlier versions of this standard also allowed the -number and +number options.to: Versions of this standard earlier than Issue 6 also allowed the -number and +number options. On page 3394 line 115663 section sort, change: An earlier version of this standard contained wording that did not make it clearto: Versions of this standard earlier than Issue 7 contained wording that did not make it clear On page 3398 line 115829 section split, change: Earlier versions of this standard allowed a -line_count option.to: Versions of this standard earlier than Issue 6 allowed a -line_count option. On page 3421 line 116688 section tail, change: Earlier versions of this standard allowed the following forms in the SYNOPSISto: Versions of this standard earlier than Issue 6 allowed the following forms in the SYNOPSIS On page 3422 line 116705 section tail, change: Earlier versions of this standard did not state any requirement for the case whereto: Versions of this standard earlier than Issue 7 did not state any requirement for the case where On page 3500 line 119461 section uniq, change: Earlier versions of this standard allowed the -number and +number options.to: Versions of this standard earlier than Issue 6 allowed the -number and +number options. On page 3629 line 124347 section yacc, change: Earlier versions of this standard did not require the code file created by yacc to containto: Versions of this standard earlier than Issue 8 did not require the code file created by yacc to contain On page 3629 line 124358 section yacc, change: Earlier versions of this standard were also silent about a declaration of main().to: Versions of this standard earlier than Issue 8 were also silent about a declaration of main(). On page 3640 line 124555 section A.1.6, change: The term ``legacy'' was included in earlier versions of this standardto: The term ``legacy'' was included in versions of this standard earlier than Issue 7 On page 3641 line 124611 section A.1.6, change: In earlier versions of this standard this was also sometimes used to refer toto: In versions of this standard earlier than Issue 7 this was also sometimes used to refer to On page 3642 line 124622 section A.1.8, change: This is based on the notation used in earlier versions of The Open Group Base specifications.to: This is based on the notation used in versions of The Open Group Base specifications earlier than Issue 6. On page 3652 line 124994 section A.3 (CPU Time), change: the Threads option that existed in earlier versions of this standard.to: the Threads option that existed in versions of this standard earlier than Issue 7. On page 3667 line 125567 section A.3 (Symbolic Constant), change: Earlier versions of this standard used a variety of termsto: Versions of this standard earlier than Issue 7 used a variety of terms On page 3668 line 125602 section A.3 (Symbolic Link), change: Earlier versions of this standard did not require symbolic links to haveto: Versions of this standard earlier than Issue 7 did not require symbolic links to have On page 3668 line 125624 section A.3 (Symbolic Link), change: Earlier versions of this standard required link() to follow symbolic linksto: Versions of this standard earlier than Issue 7 required link() to follow symbolic links On page 3677 line 125947 section A.4.4, change: Earlier versions of this standard did not make clear that directory modificationsto: Versions of this standard earlier than Issue 8 did not make clear that directory modifications On page 3680 line 126060 section A.4.11, change: Earlier versions of this standard did not specify the behavior of aio_fsync(),to: Versions of this standard earlier than Issue 8 did not specify the behavior of aio_fsync(), On page 3683 line 126205 section A.4.16, change: Earlier versions of this standard were not specific about the distinction betweento: Versions of this standard earlier than Issue 6 were not specific about the distinction between On page 3683 line 126209 section A.4.16, change: An earlier version of this standard required that a pathname with a trailing <slash>to: Issue 6 of this standard required that a pathname with a trailing <slash> On page 3684 line 126267 section A.4.16, change: Earlier versions of this standard were unclear as to whether a pathnameto: Versions of this standard earlier than Issue 7 TC1 were unclear as to whether a pathname On page 3686 line 126346 section A.4.20, change: the Semaphores option that existed in earlier versions of this standard.to: the Semaphores option that existed in versions of this standard earlier than Issue 7. On page 3689 line 126454 section A.6.2, change: Earlier versions of this standard did not state the requirement that the POSIX localeto: Versions of this standard earlier than Issue 7 TC2 did not state the requirement that the POSIX locale On page 3692 line 126592 section A.7.1, change: Earlier versions of this standard stated that if different character sets are usedto: Versions of this standard earlier than Issue 8 stated that if different character sets are used On page 3719 line 127731 section A.11.1.1, change: applications written for earlier versions of this standard which need to opento: applications written for versions of this standard earlier than Issue 7 which need to open On page 3725 line 127979 section A.12.1, change: Earlier versions of this standard included obsolescent syntax which showed some optionsto: Versions of this standard earlier than Issue 7 included obsolescent syntax which showed some options On page 3727 line 128091 section A.12.2, change: In earlier versions of this standard, all information concerningto: In versions of this standard earlier than Issue 7, all information concerning On page 3744 line 128671 section B.2.3 (ENOTSUP), change: In some earlier versions of this standard, the difference between [ENOTSUP] and [ENOSYS] wasto: In versions of this standard earlier than Issue 7 TC2, the difference between [ENOTSUP] and [ENOSYS] was On page 3746 line 128764 section B.2.3, change: error codes for these functions for compatibility with earlier versions of this standard.to: error codes for these functions for compatibility with versions of this standard earlier than Issue 6. On page 3752 line 129038 section B.2.4.2, change: the Realtime Signals Extension option that existed in earlier versions of this standard.to: the Realtime Signals Extension option that existed in versions of this standard earlier than Issue 7. On page 3865 line 133898 section C.1.7, change: Earlier versions of this standard required that all of the regular built-in utilitiesto: Versions of this standard earlier than Issue 8 required that all of the regular built-in utilities On page 3873 line 134237 section C.2.4, change: Earlier versions of this standard omitted time from this listto: Versions of this standard earlier than Issue 8 omitted time from this list On page 3880 line 134602 section C.2.6, change: Earlier versions of the shell used it for splitting all fieldsto: Historical versions of the shell used it for splitting all fields On page 3882 line 134676 section C.2.6.1, change: and earlier versions of this standard reflected this.to: and versions of this standard earlier than Issue 7 reflected this. On page 3891 line 135062 section C.2.7.2, change: Earlier versions of this standard did not require redirection usingto: Versions of this standard earlier than Issue 8 did not require redirection using On page 3909 line 135821 section C.2.14.1, change: Earlier versions of this standard allowed two behaviors when a pattern ends withto: Versions of this standard earlier than Issue 8 allowed two behaviors when a pattern ends with On page 3909 line 135825 section C.2.14.1, change: Earlier versions of this standard included the statementto: Versions of this standard earlier than Issue 8 included the statement |
||||||||||||
Tags | tc1-2024 | ||||||||||||
Attached Files | |||||||||||||
|
There are no notes attached to this issue. |
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |