View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
00018741003.1(2024)/Issue8Base Definitions and Headerspublic2024-11-12 17:082024-11-14 17:25
Reportergeoffclare Assigned To 
PrioritynormalSeverityEditorialTypeError
Status ResolvedResolutionAccepted 
NameGeoff Clare
OrganizationThe Open Group
User Reference
Section3
Page Number(many)
Line Number(many)
Interp Status---
Final Accepted Text
Summary0001874: ISO editors Issue 8 comment 052
DescriptionIn their comment 052 on Issue 8 the ISO editors requested that any requirements stated in definitions be removed. The Austin Group's response was that a change would be considered for the next TC.

Where the affected requirements are already stated elsewhere they can be deleted or changed to an informative form; otherwise they should be moved.

I have only proposed changes for cases where a definition is unambiguously making requirements, e.g. by using "shall". There are many places where present tense is used and I have generally assumed that these are intended to be giving information, not making requirements.

For ease of review, where the desired action includes changes outside of XBD chapter 3 they are stated after the definition they relate to rather than in page and line number order.
Desired ActionOn page 32 line 1062 section 3.10 Alias Name, change:
In the shell command language, a word consisting solely of alphabetics and digits from the portable character set and any of the following characters: '!', '%', ',', '-', '@', '_'.

Implementations may allow other characters within alias names as an extension.

<small>Note: The Portable Character Set is defined in detail in [xref to 6.1].</small>
to:
In the shell command language, a word that can be subject to alias substitution (see [xref to XCU 2.3.1 Alias Substitution]).

On XCU page 2477 line 80277 section 2.3.1 Alias Substitution, change:
The TOKEN is a valid alias name (see [xref to XBD Section 3.10]).
to:
The TOKEN is a valid alias name. A word consisting solely of alphabetics and digits from the portable character set (see [xref to 6.1]) and any of the characters '!', '%', ',', '-', '@', and '_' shall be a valid alias name. Implementations may allow other characters within alias names as an extension.

On page 33 line 1094 section 3.18 Application, change:
A computer program that performs some desired function.

When the User Portability Utilities option is supported, requirements placed on applications relating to the use of standard utilities shall also apply to the actions of a user who is entering shell command language statements into an interactive shell.
to:
A computer program, or collection of programs, that performs some desired function.

After page 27 line 930 section 2.2 Application Conformance, add a paragraph:
When the User Portability Utilities option is supported, requirements placed on applications relating to the use of standard utilities shall also apply to the actions of a user who is entering shell command language statements into an interactive shell.

On page 52 line 1628 section 3.146 Filename, change:
A sequence of bytes consisting of 1 to {NAME_MAX} bytes used to name a file. The bytes composing the name shall not contain the <NUL> or <slash> characters. In the context of a pathname, each filename shall be followed by a <slash> or a <NUL> character; elsewhere, a filename followed by a <NUL> character forms a string (but not necessarily a character string).
to:
A sequence of bytes consisting of 1 to {NAME_MAX} bytes, other than <NUL> or <slash>, used to name a file. In a pathname, each filename is followed by a <slash> or a <NUL> character; elsewhere, a filename followed by a <NUL> character forms a string (but not necessarily a character string).

On page 55 line 1710 section 3.165 Group ID, change:
The value (gid_t)-1 shall not be a valid group ID, but does have a defined use in some interfaces defined in this standard.
to:
The value (gid_t)-1 does not identify a group, but does have a defined use in some interfaces defined in this standard.

On page 44 line 1725 section 3.169 Hole, delete:
Not all bytes with the value zero need belong to a hole; however, all seekable files shall have a virtual hole starting at the current size of the file.
(which is duplicated on the lseek() page).

On page 84 line 2557 section 3.363 Symbolic Constant, change:
Unless stated otherwise, the following shall apply to every symbolic constant:

  • It expands to a compile-time constant expression with an integer type.

  • It may be defined as another type of constant--e.g., an enumeration constant--as well as being a macro.

  • It need not be usable in #if preprocessing directives.
to:
<small>Note: Additional requirements apply to symbolic constants over and above those for other object-like macros. See [xref to XSH 2.1.2 Use and Implementation of Macros].</small>

After XSH page 496 line 17408 section 2.1.2, add:
For every macro that is a symbolic constant, in addition the following shall apply unless explicitly stated otherwise:

  • It expands to a compile-time constant expression with an integer type.

  • It may be defined as another type of constant--e.g., an enumeration constant--as well as being a macro.

  • It need not be usable in #if preprocessing directives.

On page 88 line 2672 section 3.389, change:
The value shall be unique across all threads in a process, regardless of whether the thread is:
to:
The value is unique across all threads in a process (see [xref to 2.9.2 Thread IDs]).
and move the remaining lines (2674-2683), minus the final sentence of the small-font note (ending "are defined in detail in the System Interfaces volume of POSIX.1-2024"), to the location indicated in the next change.

On XSH page 538 line 19191 section 2.9.2 Thread IDs, after:
The effect of calling any of the functions defined in this volume of POSIX.1-2024 and passing as an argument the thread ID of a thread from another process is unspecified.
add:
The value of a thread ID shall be unique across all threads in a process, regardless of whether the thread is:
followed by the moved lines from the previous change.

On page 89 line 2702-2709 section 3.393 Thread-Safe, move the entire definition, minus the second sentence ("Each function defined in the System Interfaces volume of POSIX.1-2024 is thread-safe unless explicitly stated otherwise.") to the beginning of XSH 2.9.1 Thread-Safety at page 537 line 19147.

On page 89 line 2702 section 3.393 Thread-Safe, insert a new definition:
A thread-safe function is one that avoids data races with other calls to the same function, and with calls to any other thread-safe functions, by multiple threads.

<small>Note: Thread-Safety is defined in detail in [xref to XSH 2.9.1].</small>

On page 91 line 2770 section 3.408 User ID, change:
The value (uid_t)-1 shall not be a valid user ID, but does have a defined use in some interfaces defined in this standard.
to:
The value (uid_t)-1 does not identify a user, but does have a defined use in some interfaces defined in this standard.

Tagstc1-2024

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2024-11-12 17:08 geoffclare New Issue
2024-11-12 17:08 geoffclare Name => Geoff Clare
2024-11-12 17:08 geoffclare Organization => The Open Group
2024-11-12 17:08 geoffclare Section => 3
2024-11-12 17:08 geoffclare Page Number => (many)
2024-11-12 17:08 geoffclare Line Number => (many)
2024-11-12 17:08 geoffclare Interp Status => ---
2024-11-14 17:25 Don Cragun Status New => Resolved
2024-11-14 17:25 Don Cragun Resolution Open => Accepted
2024-11-14 17:26 Don Cragun Tag Attached: tc1-2024