The following issue has been SUBMITTED.
======================================================================
https://austingroupbugs.net/view.php?id=1869
======================================================================
Reported By: geoffclare
Assigned To:
======================================================================
Project: 1003.1(2024)/Issue8
Issue ID: 1869
Category: Base Definitions and Headers
Type: Error
Severity: Editorial
Priority: normal
Status: New
Name: Geoff Clare
Organization: The Open Group
User Reference:
Section: (many)
Page Number: (many)
Line Number: (many)
Interp Status: ---
Final Accepted Text:
======================================================================
Date Submitted: 2024-11-05 14:58 UTC
Last Modified: 2024-11-05 14:58 UTC
======================================================================
Summary: 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:<blockquote><small><b>Note:</b> This may also be written as ``line
on the display''.</small></blockquote>
(as this note is the only place where that phrase appears).
On page 47 line 1497 section 3.115 Driver, change:<blockquote>A driver may
contain</blockquote>to:<blockquote>A driver can contain</blockquote>
On page 70 line 2142 section 3.264 Portable Filename, and
page 98 line 2956 section 4.10 Filename Portability,
change:<blockquote>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.</blockquote>to:<blockquote>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.</blockquote>
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:<blockquote>implementations may have extensions that allow it to be
changed</blockquote>to:<blockquote>it is possible for implementations to
have extensions that allow it to be changed</blockquote>
On page 96 line 2890 section 4.3 Default Initialization,
change:<blockquote>For consistent results, portable applications comparing
structures should test each field
individually.</blockquote>to:<blockquote>Portable applications can achieve
consistent results when comparing structures by testing each field
individually.</blockquote>
On page 98 line 2969 section 4.11 File System Cache,
change:<blockquote>later operations' effects may be present in storage with
earlier effects missing</blockquote>to:<blockquote>it is possible for later
operations' effects to be present in storage with earlier effects
missing</blockquote>
On page 98 line 2972 section 4.11 File System Cache,
change:<blockquote>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 <i>write</i>() may be
transferred; or <tt>rename("a","b")</tt> may result in <b>b</b> being
created without <b>a</b> being removed.</blockquote>to:<blockquote>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 <i>write</i>() to be transferred, or for
<tt>rename("a","b")</tt> to result in <b>b</b> being created without
<b>a</b> being removed.</blockquote>
On page 98 line 2977 section 4.11 File System Cache,
change:<blockquote>some file systems may support non-conforming
configurations</blockquote>to:<blockquote>it is possible for some file
systems to support non-conforming configurations</blockquote>
On page 100 line 3062 section 4.15.1.1 Data Races,
change:<blockquote>different threads may
observe</blockquote>to:<blockquote>it is possible for different threads to
observe</blockquote>
On page 135 line 4404 section 7.3.1 LC_CTYPE, change:<blockquote>but shall
automatically belong to</blockquote>to:<blockquote>but automatically
belongs to</blockquote>
On page 140 line 4629 section 7.3.2 LC_COLLATE, change:<blockquote>Users
installing their own locales should ensure that they
define</blockquote>to:<blockquote>Users installing their own locales can
prevent unexpected results by ensuring that they define</blockquote>
On page 140 line 4634 section 7.3.2 LC_COLLATE, change:<blockquote>Unusual
behavior may result</blockquote>to:<blockquote>It is possible for unusual
behavior to result</blockquote>
On page 154 line 5258 section 7.3.5.1 LC_TIME Locale Definition,
change:<blockquote>The start of an era might not be the earliest point in
the era--it may be the latest.</blockquote>to:<blockquote>It is possible
for the start of an era to be the latest point in the era instead of the
earliest.</blockquote>
On page 167 line 5832 section 8.1 Environment Variable Definition,
change:<blockquote>Other applications may have
difficulty</blockquote>to:<blockquote>It is possible for other applications
to have difficulty</blockquote>
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:<blockquote>A future version of this standard
may</blockquote>to:<blockquote>A future version of this standard is
expected to</blockquote>
On page 209 line 7526 section 11.2.4 Control Modes,
change:<blockquote>which may not be the same as
baud</blockquote>to:<blockquote>which is not necessarily the same as
baud</blockquote>
On page 369 line 12911 section <stdint.h>, change:<blockquote>the actual
type may use more bits than that</blockquote>to:<blockquote>it is possible
for the actual type to use more bits than that</blockquote>
On page 2468 line 79945 section 1.4 Utility Description Defaults,
change:<blockquote><small><b>Note:</b> 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.</small></blockquote>to:<blockquote>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.
<small><b>Note:</b> A future version of this standard is expected to
require that utilities treat this as an error.</small></blockquote>
On page 2473 line 80098 section 2.2 Quoting, change:<blockquote>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.</blockquote>to:<blockquote>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.</blockquote>
On page 2546 line 83028 section export, change:<blockquote>the results may
be undefined.</blockquote>to:<blockquote>the results are
undefined.</blockquote>
On page 2965 line 99083 section get, change:<blockquote>A branch delta may
always be created from a non-leaf delta.</blockquote>to:<blockquote>A
branch delta can always be created from a non-leaf delta.</blockquote>
On page 3078 line 103304 section ls, change:<blockquote>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), <b>-C</b> should not be used when filenames might
be extracted from the output by a script.</blockquote>to:<blockquote>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 <b>-C</b> can cause unexpected results
when filenames are extracted from the output by a script.</blockquote>
On page 3229 line 109173 section od, change:<blockquote><small><b>Note:</b>
The "\012" value may be written either as <b>lf</b> or
<b>nl</b>.</small></blockquote>to:<blockquote>The "\012" value may be
written either as <b>lf</b> or <b>nl</b>.</blockquote>
On page 3737 line 128368 section B.2.2.1 POSIX.1 Symbols,
change:<blockquote>They should not be confused with the version test
macros</blockquote>to:<blockquote>They are not to be confused with the
version test macros</blockquote>
======================================================================
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 => ---
======================================================================
