0001869: ISO editors Issue 8 comment 055 - Austin Group Defect Tracker

Austin Group Defect Tracker

Aardvark Mark IV

Viewing Issue Simple Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Category

Severity

Type

Date Submitted

Last Update

0001869

[1003.1(2024)/Issue8] Base Definitions and Headers

Editorial

Error

2024-11-05 14:58

2024-11-07 16:30

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

0001869: ISO editors Issue 8 comment 055

Description

In their comment 055 on Issue 8 the ISO editors requested that uses of "shall", "should", or "may" in notes be changed to use alternative wording. The Austin Group's response was that this change would be considered for the next TC.

In a few cases the solution should be to leave the text as-is and make it normative instead.

The suggested changes avoid using "might", as that is another of the ISO editors' requests.

Desired Action

On page 46 line 108 section 3.108 Display Line, delete:

Note: This may also be written as ``line on the display''.

(as this note is the only place where that phrase appears).

On page 47 line 1497 section 3.115 Driver, change:

A driver may contain

to:

A driver can contain

On page 70 line 2142 section 3.264 Portable Filename, and
page 98 line 2956 section 4.10 Filename Portability, change:

Applications should avoid using filenames that have the <hyphen-minus> character as the first character since this may cause problems when filenames are passed as command line arguments.

to:

Avoiding the use of filenames that have the <hyphen-minus> character as the first character prevents problems when filenames are passed as command line arguments.

On page 82 line 2491 section 3.353 Standard Error, and
page 83 line 2499 section 3.354 Standard Input, and
page 83 line 2508 section 3.355 Standard Output, change:

implementations may have extensions that allow it to be changed

to:

it is possible for implementations to have extensions that allow it to be changed

On page 96 line 2890 section 4.3 Default Initialization, change:

For consistent results, portable applications comparing structures should test each field individually.

to:

Portable applications can achieve consistent results when comparing structures by testing each field individually.

On page 98 line 2969 section 4.11 File System Cache, change:

later operations' effects may be present in storage with earlier effects missing

to:

it is possible for later operations' effects to be present in storage with earlier effects missing

On page 98 line 2972 section 4.11 File System Cache, change:

Operations that create [...] may have only part of their effects transferred to storage, and after a crash these operations may appear to have been only partly done, with the parts not necessarily done in any order. For example, only the second half of a write() may be transferred; or <tt>rename("a","b")</tt> may result in b being created without a being removed.

to:

It is possible for operations that create [...] to have only part of their effects transferred to storage, and after a crash it is possible for these operations to appear to have been only partly done, with the parts not necessarily done in any order. For example, it is possible for only the second half of a write() to be transferred, or for <tt>rename("a","b")</tt> to result in b being created without a being removed.

On page 98 line 2977 section 4.11 File System Cache, change:

some file systems may support non-conforming configurations

to:

it is possible for some file systems to support non-conforming configurations

On page 100 line 3062 section 4.15.1.1 Data Races, change:

different threads may observe

to:

it is possible for different threads to observe

On page 135 line 4404 section 7.3.1 LC_CTYPE, change:

but shall automatically belong to

to:

but automatically belongs to

On page 140 line 4629 section 7.3.2 LC_COLLATE, change:

Users installing their own locales should ensure that they define

to:

Users installing their own locales can prevent unexpected results by ensuring that they define

On page 140 line 4634 section 7.3.2 LC_COLLATE, change:

Unusual behavior may result

to:

It is possible for unusual behavior to result

On page 154 line 5258 section 7.3.5.1 LC_TIME Locale Definition, change:

The start of an era might not be the earliest point in the era--it may be the latest.

to:

It is possible for the start of an era to be the latest point in the era instead of the earliest.

On page 167 line 5832 section 8.1 Environment Variable Definition, change:

Other applications may have difficulty

to:

It is possible for other applications to have difficulty

On page 181 line 6433 section 9.3.2 BRE Ordinary Characters, and
page 2477 line 80296 section 2.3.1 Alias Substitution, and
page 2485 line 80631 section 2.6.1 Tilde Expansion, and
page 2494 line 80997 section 2.7 Redirection, and
page 2526 line 82332 section 2.14.3 Patterns Used for Filename Expansion, change:

A future version of this standard may

to:

A future version of this standard is expected to

On page 209 line 7526 section 11.2.4 Control Modes, change:

which may not be the same as baud

to:

which is not necessarily the same as baud

On page 369 line 12911 section <stdint.h>, change:

the actual type may use more bits than that

to:

it is possible for the actual type to use more bits than that

On page 2468 line 79945 section 1.4 Utility Description Defaults, change:

Note: If the requested action is to write one or more pathnames in a format that has <newline> as a terminator or separator, and a pathname to be written contains any bytes that have the encoded value of a <newline> character, this should be treated as an action that cannot be performed. A future version of this standard may require that utilities treat this as an error.

to:

If the requested action is to write one or more pathnames in a format that has <newline> as a terminator or separator, and a pathname to be written contains any bytes that have the encoded value of a <newline> character, this should be treated as an action that cannot be performed.

Note: A future version of this standard is expected to require that utilities treat this as an error.

On page 2473 line 80098 section 2.2 Quoting, change:

A future version of this standard may extend the conditions under which these characters are special. Therefore applications should quote them whenever they are intended to represent themselves.

to:

A future version of this standard could extend the conditions under which these characters are special. Therefore potential future problems can be avoided by quoting them whenever they are intended to represent themselves.

On page 2546 line 83028 section export, change:

the results may be undefined.

to:

the results are undefined.

On page 2965 line 99083 section get, change:

A branch delta may always be created from a non-leaf delta.

to:

A branch delta can always be created from a non-leaf delta.

On page 3078 line 103304 section ls, change:

Since the output from this option may use separator characters that include characters that might appear in filenames (in addition to the problems related to <newline>s in filenames), -C should not be used when filenames might be extracted from the output by a script.

to:

Since it is possible for the separator characters used in the output from this option to appear in filenames (in addition to the problems related to <newline>s in filenames), specifying -C can cause unexpected results when filenames are extracted from the output by a script.

On page 3229 line 109173 section od, change:

Note: The "\012" value may be written either as lf or nl.

to:

The "\012" value may be written either as lf or nl.

On page 3737 line 128368 section B.2.2.1 POSIX.1 Symbols, change:

They should not be confused with the version test macros

to:

They are not to be confused with the version test macros

Issue History
Date Modified	Username	Field	Change
2024-11-05 14:58	geoffclare	New Issue
2024-11-05 14:58	geoffclare	Name	=> Geoff Clare
2024-11-05 14:58	geoffclare	Organization	=> The Open Group
2024-11-05 14:58	geoffclare	Section	=> (many)
2024-11-05 14:58	geoffclare	Page Number	=> (many)
2024-11-05 14:58	geoffclare	Line Number	=> (many)
2024-11-05 14:58	geoffclare	Interp Status	=> ---
2024-11-07 16:30	Don Cragun	Status	New => Resolved
2024-11-07 16:30	Don Cragun	Resolution	Open => Accepted
2024-11-07 16:31	Don Cragun	Tag Attached: tc1-2024

Relationships