0001878: ISO editors Issue 8 comments 061+072 - Austin Group Defect Tracker

Austin Group Defect Tracker

Aardvark Mark IV

Viewing Issue Simple Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Category

Severity

Type

Date Submitted

Last Update

0001878

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

Editorial

Error

2024-11-19 15:10

2024-11-21 16:50

Reporter

geoffclare

View Status

public

Assigned To

Priority

normal

Resolution

Accepted As Marked

Status

Resolved

Name

Geoff Clare

Organization

The Open Group

User Reference

Section

(many)

Page Number

(many)

Line Number

(many)

Interp Status

---

Final Accepted Text

See Note: 0006968.

Summary

0001878: ISO editors Issue 8 comments 061+072

Description

In their comments 061 and 072 on Issue 8 the ISO editors requested that uses of "might" be changed to other wording. The Austin Group's response was that a change would be considered for the next TC.

So far I have only considered uses in normative text and in small-font notes within normative text. There are too many in other informative text to address them all in a "quick" TC.

Some of the uses came from C17, and in those cases the proposed new wording is taken from the latest C2Y draft.

Desired Action

On page 7 line 147 section 1.8 Portability, change:

describe functionality that might not be fully portable to systems meeting the requirements for POSIX conformance

to:

describe functionality that is not fully portable to all systems meeting the requirements for POSIX conformance

On page 25 line 833 section 2.1.6 Options, change:

For example, an old application binary might be run on a newer implementation to which support for the option has been added.

to:

For example, an old application binary could be run on a newer implementation to which support for the option has been added.

On page 25 line 841 section 2.1.6 Options, change:

Option might or might not be supported at runtime.

The implementation advertises at compile time (by defining the constant in <unistd.h> with value zero) that the option is supported for compilation and might or might not be supported at runtime.

to:

Option supported for compilation and possibly supported at runtime.

The implementation advertises at compile time (by defining the constant in <unistd.h> with value zero) that the option is supported for compilation and is possibly supported at runtime.

On page 39 line 1255 section 3.55 Byte, change:

The definition of byte from the ISO C standard is broader than the above and might accommodate hardware architectures with different sized addressable units than octets.

to:

The definition of byte from the ISO C standard is broader than the above and accommodates hardware architectures with different sized addressable units than octets.

On page 44 line 1417 section 3.90 CPU Time, change:

With this definition the sum of all the execution times of all the threads in a process might not equal the process execution time

to:

With this definition it is possible that the sum of all the execution times of all the threads in a process does not equal the process execution time

On page 68 line 2091 section 3.254 Pathname, change:

otherwise, the pathname might only be a string (rather than a character string).

to:

otherwise, it is possible that the pathname is only a string (rather than a character string).

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

a structure initialized using { 0 } might not memcmp() as equal to

to:

it is possible that a structure initialized using { 0 } does not memcmp() as equal to

On page 99 line 3019 section 4.13 Host and Network Byte Orders, change:

Bits might not be allocated to bytes in any obvious order at all.

to:

It is possible that bits are not be allocated to bytes in any obvious order at all.

On page 102 line 3125 section 4.15.1.1 Data Races, change:

The set of side effects from which a given evaluation might take its value is also restricted

to:

The set of side effects from which a given evaluation can take its value is also restricted

On page 104 line 3209 section 4.15.2 Memory Synchronization, change:

no thread of control can read or modify a memory location while another thread of control might be modifying it.

to:

no thread of control can read or modify a memory location while another thread of control could be modifying it.

On page 110 line 3473 section 4.24 Treatment of NaN Arguments ..., change:

The function might never see the signaling NaN, since it might trigger when the arguments are

to:

It is possible that the function never sees the signaling NaN, since it could trigger when the arguments are

On page 111 line 3483 section 4.25 Utility, change:

such as might be produced by a compiler

to:

such as could be produced by a compiler

On page 131 line 4250 section 7.3.1 LC_CTYPE, change:

it might not be possible for conforming applications to work properly.

to:

it is possible that conforming applications will not work properly.

On page 171 line 6020 section 8.2 Internationalization Variables, change:

directory names that might be used in NLSPATH should not include a <colon> character.

to:

directory names that could be used in NLSPATH should not include a <colon> character.

On page 175 line 6185 section 8.3 Other Environment Variables, change:

directory names that might be used in PATH should not include a <colon> character.

to:

directory names that could be used in PATH should not include a <colon> character.

On page 194 line 6983 section 9.5.2 RE and Bracket Expression Grammar, change:

that might be interpreted as anchors.

to:

that could be interpreted as anchors.

On page 253 line 8871 section <fenv.h>, change:

when an application might access the floating-point environment

to:

when an application can access the floating-point environment

On page 282 line 9772 section <limits.h>, change:

This indetermination might depend on the amount of available memory

to:

This indetermination could depend on the amount of available memory

On page 374 line 13122 section <stdint.h>, change:

UINT64_C(0x123) might expand to the integer constant 0x123ULL.

to:

UINT64_C(0x123) can expand to the integer constant 0x123ULL.

On page 433 line 15052 section <sys/wait.h>, change:

A core image might or might not have been produced.

to:

It is possible that a core image was not produced.

On page 458 line 15976 section <unistd.h>, change:

the option shall be supported for compilation and might or might not be supported at runtime.

to:

the option shall be supported for compilation and is possibly supported at runtime.

On page 475 line 16732 section <unistd.h>, change:

Option might or might not be supported.

to:

Option supported for compilation and possibly supported at runtime.

On page 496 line 17416 section 2.2.1 POSIX.1 Symbols, change:

control the visibility of symbols that might be included in a header.

to:

control the visibility of symbols included in a header.

On page 524 line 18589 section 2.5.1 Interaction of File Descriptors and ..., change:

This might occur during functions such as a fork() or _exit().

to:

This could occur during functions such as fork() or _exit().

On page 539 line 19232 section 2.9.3 Thread Mutexes, change:

Depending on the mutex type, it might be possible for another thread to unlock the mutex and recover the state of the mutex.

to:

Depending on the mutex type, it is possible that another thread could unlock the mutex and recover the state of the mutex.

On page 552 line 19722 section 2.10.11 Socket Receive Queue, change:

the complete record might never be present in the receive buffer at one time, as a portion might already have been returned to the application, and another portion might not yet have been received from the communications provider

to:

it is possible that the complete record is never present in the receive buffer at one time, as a portion could already have been returned to the application, and another portion could be yet to be received from the communications provider

On page 563 line 20205 section 2.12 Status Information, change:

A process might not have any status information

to:

It is possible that a process does not have any status information

On page 651 line 22832 section atomic_init(), change:

initializing any additional state that the implementation might need to carry

to:

initializing any additional state that the implementation may need to carry

On page 657 line 23026 section basename(), and
page 811 line 27766 section dirname(), change:

The returned pointer might be invalidated if

to:

The returned pointer may be invalidated if

On page 668 line 23427 section bindtextdomain(), change:

A subsequent call to bind_textdomain_codeset() with a non-empty domainname argument might invalidate the returned pointer or overwrite the string content. The returned pointer might also be invalidated if the calling thread is terminated.

to:

A subsequent call to bind_textdomain_codeset() with a non-empty domainname argument may invalidate the returned pointer or overwrite the string content. The returned pointer may also be invalidated if the calling thread is terminated.

On page 761 line 26261 section cnd_timedwait(), change:

the dynamic binding between condition variable and mutex might be removed

to:

the dynamic binding between condition variable and mutex could be removed

On page 797 line 27312 section ctermid(), and
page 819 line 28021 section dlerror(), and
page 1143 line 39117 section getlogin(), and
page 1829 line 60406 section ptsname(), and
page 2167 line 70814 section strsignal(), and
page 2307 line 75095 section ttyname(), change:

The returned pointer might be invalidated or the string content might be overwritten by a subsequent call

to:

The returned pointer may be invalidated or the string content may be overwritten by a subsequent call

On page 797 line 27314 section ctermid(), and
page 819 line 28023 section dlerror(), and
page 2167 line 70815 section strsignal(), change:

The returned pointer might also be invalidated if the calling thread is terminated.

to:

The returned pointer may also be invalidated if the calling thread is terminated.

On page 1143 line 39119 section getlogin(), and
page 1829 line 60407 section ptsname(), and
page 2307 line 75096 section ttyname(), change:

The returned pointer and the string content might also be invalidated if the calling thread is terminated.

to:

The returned pointer and the string content may also be invalidated if the calling thread is terminated.

On page 815 line 27893 section dladdr(), change:

all regular files mapped using mmap() might be included

to:

all regular files mapped using mmap() may be included

On page 815 line 27900 section dladdr(), change:

This might no longer resolve to the file that was mapped

to:

It is possible that this no longer resolves to the file that was mapped

On page 817 line 27956 section dlclose(), change:

For instance, an executable object file that had been loaded with a dlopen() operation specifying the RTLD_GLOBAL flag might provide a target for dynamic relocations performed in the processing of other relocatable objects--in such environments, an application may assume that no relocation, once made, shall be undone or remade unless the executable object file containing the relocated object has itself been removed.

to:

For instance, an executable object file that had been loaded with a dlopen() operation specifying the RTLD_GLOBAL flag could provide a target for dynamic relocations performed in the processing of other relocatable objects--in such environments, an application can assume that no relocation, once made, will be undone or remade unless the executable object file containing the relocated object has itself been removed.

On page 821 line 28099 section dlopen(), change:

Specifying RTLD_LAZY should improve performance on implementations supporting dynamic symbol binding since a process might not reference all of the symbols

to:

Specifying RTLD_LAZY can improve performance on implementations supporting dynamic symbol binding since it is possible that a process does not reference all of the symbols

On page 822 line 28134 section dlopen(), change:

To resolve the ambiguities such a situation might present

to:

To resolve the ambiguities that are possible in such a situation

On page 840 line 28731 section getgrent(), and
page 842 line 28799 section gethostent(), and
page 844 line 28867 section endnetent(), and
page 846 line 28934 section endprotoent(), and
page 848 line 28995 section endpwent(), and
page 851 line 29094 section endservent(), and
page 1128 line 38645 section getgrgid(), and
page 1132 line 38783 section getgrnam(), and
page 1166 line 39840 section getpwnam(), and
page 1170 line 39984 section getpwuid(), and
page 1858 line 61294 section readdir(), change:

The returned pointer, and pointers within the structure, might be invalidated or the structure or the storage areas might be overwritten

to:

The returned pointer, and pointers within the structure, may be invalidated or the structure or the storage areas may be overwritten

On page 840 line 28733 section getgrent(), and
page 842 line 28801 section gethostent(), and
page 844 line 28869 section endnetent(), and
page 846 line 28936 section endprotoent(), and
page 848 line 28997 section endpwent(), and
page 851 line 29096 section endservent(), and
page 1128 line 38647 section getgrgid(), and
page 1132 line 38785 section getgrnam(), and
page 1166 line 39842 section getpwnam(), and
page 1170 line 39986 section getpwuid(), and
page 1858 line 61297 section readdir(), change:

The returned pointer, and pointers within the structure, might also be invalidated if the calling thread is terminated.

to:

The returned pointer, and pointers within the structure, may also be invalidated if the calling thread is terminated.

On page 868 line 29534 section exec, and
page 1582 line 53118 section posix_spawn(), and
page 2503 line 81343 section 2.9.1.5 Standard File Descriptors, change:

consequently the utility or application might not behave as described in this standard.

to:

consequently it is possible that the utility or application does not behave as described in this standard.

On page 972 line 33059 section fmtmsg(), change:

Indicates a condition that is out of the ordinary, that might be a problem, and should be watched.

to:

Indicates a condition that is out of the ordinary, that could be a problem, and should be watched.

On page 1141 line 39050 section getlocalename_l(), change:

the returned string pointer might be invalidated or the string content might be overwritten by a subsequent call in the same thread to getlocalename_l() with LC_GLOBAL_LOCALE; the returned string pointer might also be invalidated if the calling thread is terminated.

to:

the returned string pointer may be invalidated or the string content may be overwritten by a subsequent call in the same thread to getlocalename_l() with LC_GLOBAL_LOCALE; the returned string pointer may also be invalidated if the calling thread is terminated.

On page 1188 line 40522 section getsubopt(), change:

is one of the possible tokens that might be found in

to:

is one of the tokens it is possible to find in

On page 1351 line 45395-45401 section localeconv(), change all uses of "might" to "may" in the RETURN VALUE section.

On page 1475 line 49504 section msgrcv(), and
page 1478 line 49611 section msgsnd(), change:

example of what this user-defined buffer might look like

to:

example of what this user-defined buffer could look like

On page 1510 line 50630-50639 section nl_langinfo(), change all uses of "might" to "may" in the RETURN VALUE section.

On page 1543 line 51632 section poll(), and
page 1636 line 54581 section pselect(), change:

The function might return data, an end-of-file indication, or

to:

The function could return data, an end-of-file indication, or

On page 1558 line 52228 section posix_devctl(), change:

Corresponding data might be transferred, partially transferred, or

to:

Corresponding data may be transferred, partially transferred, or

On page 1734 line 57636 section pthread_key_create(), change:

even though this might result in an infinite loop.

to:

even though this could result in an infinite loop.

On page 1885 line 62265 section regcomp(), change:

any given parenthesized subexpression of pattern might participate in the match of several different substrings of string, or it might not match any substring

to:

it is possible that any given parenthesized subexpression of pattern participates in the match of several different substrings of string, or that it does not match any substring

On page 1887 line 62333 section regcomp(), change:

but it might not be as detailed under some implementations.

to:

but it may be less detailed under some implementations.

On page 1991 line 65530 section setlocale(), change:

<CX>The returned string pointer might be invalidated or</CX> the string content might be overwritten by a subsequent call to setlocale(). <CX>The returned pointer might also be invalidated if the calling thread is terminated.</CX>

to:

<CX>The returned string pointer may be invalidated or</CX> the string content may be overwritten by a subsequent call to setlocale(). <CX>The returned pointer may also be invalidated if the calling thread is terminated.</CX>

On page 2125 line 69391 section strerror(), change:

<CX>The returned string pointer might be invalidated or</CX> the string content might be overwritten by a subsequent call to strerror(), <CX>or by a subsequent call to strerror_l() in the same thread. The returned pointer and the string content might also be invalidated if the calling thread is terminated.</CX>

to:

<CX>The returned string pointer may be invalidated or</CX> the string content may be overwritten by a subsequent call to strerror(), <CX>or by a subsequent call to strerror_l() in the same thread. The returned pointer and the string content may also be invalidated if the calling thread is terminated.</CX>

On page 2207 line 72088 section system(), change:

this might then cause the program calling system() to behave

to:

this can then cause the process calling system() to behave

On page 2207 line 72097 section system(), change:

If this might cause the application to miss a signal

to:

If this could cause the application to miss a signal

On page 2253 line 73523 section thrd_create(), change:

A thread's identifier might be reused for a different thread

to:

A thread's identifier can be reused for a different thread

On page 2258 line 73679 section thrd_exit(), change:

calling any atexit() routines that might exist.

to:

calling any atexit() routines that exist.

On page 2472 line 80094 section 2.2 Quoting, change:

and the following might need to be quoted under certain circumstances.

to:

and the following need to be quoted under certain circumstances.

On page 2489 line 80787 section 2.6.3 Command Substitution, change:

however, they might be treated as field delimiters and eliminated during field splitting

to:

however, it is possible that they will be treated as field delimiters and eliminated during field splitting

On page 2492 line 80901 section 2.6.5 Field Splitting, change:

The locale might have changed between those events.

to:

The locale could have changed between those events.

On page 2493 line 80953 section 2.6.5 Field Splitting, change:

The ordered list of output fields so produced, which might be empty,

to:

The ordered list of output fields so produced, which can be empty,

On page 2514 line 81807 section 2.10.2 Shell Grammar Rules, change:

Each TOKEN that might either be expanded or have assignment applied to it

to:

Each TOKEN that would either be expanded or have assignment applied to it

On page 2631 line 86291 section awk, change:

One convention that might not be obvious from the formal grammar is

to:

One convention that is not be obvious from the formal grammar is

On page 2676 line 88152 section c17, change:

be aware that binary data placed in shared memory or in files might not be recognized by applications

to:

be aware that it is possible for binary data placed in shared memory or in files not to be recognized by applications

On page 2776 line 91907 section dd, change:

this might entail multiple reads

to:

this could entail multiple reads

On page 2844 line 94452 section ex, change:

the first time a file that already exists (including a file that might not exist but for which recovery information is available, when the -r option is specified) replaces

to:

the first time a file that already exists (or a file that does not exist but for which recovery information is available, when the -r option is specified) replaces

On page 2956 line 98812 section fuser, change:

For example, fuser might first write the information for all file operands to standard error and then write all of the process IDs to standard output.

to:

For example, fuser could first write the information for all file operands to standard error and then write all of the process IDs to standard output.

On page 3021 line 101095 section jobs, change:

some process IDs might have been removed from the list but not successfully reported.

to:

some process IDs may have been removed from the list but not successfully reported.

On page 3116 line 104833 section mailx, change:

any commands that might previously have marked the messages to be deleted

to:

any commands that could previously have marked the messages to be deleted

On page 3191 line 107764 section msgfmt, change:

shall detect and diagnose input file abnormalities which might represent translation errors.

to:

shall detect and diagnose input file abnormalities which could represent translation errors.

On page 3194 line 107918 section msgfmt, change:

They can be added, as might "#." prefixed additional comments

to:

They can be added, as can "#." prefixed additional comments

On page 3195 line 107922 section msgfmt, change:

This flag indicates that the msgstr string might not be a correct translation

to:

This flag indicates that the msgstr string is possibly not a correct translation

On page 3274 line 110990 section pax, change:

meets any selection criteria that might be imposed on the format-reading utility by the user

to:

meets any selection criteria imposed on the format-reading utility by the user

On page 3619 line 123920 section yacc, change:

actions within rules might introduce conflicts that would not otherwise exist.

to:

actions within rules could introduce conflicts that would not otherwise exist.

On page 3622 line 124052 section yacc, change:

Some grammar rules might not have both precedence and associativity.

to:

It is possible for some grammar rules not to have both precedence and associativity.

Tags

Relationships

Notes
(0006967) Don Cragun (manager) 2024-11-19 22:49 edited on: 2024-11-19 22:51	There is a typo in Desired Action in the to: section of the suggested change: On page 2631 line 86291 section awk, change: One convention that might not be obvious from the formal grammar is to: One convention that is not be obvious from the formal grammar is Change: "is not be obvious" to: "is not obvious".

(0006968) Don Cragun (manager) 2024-11-21 16:47 edited on: 2024-11-21 17:02	Make the changes suggested in the Desired action as modified by the correction noted in Note: 0006967 and the following: In: On page 99 line 3019 section 4.13 Host and Network Byte Orders, change: Bits might not be allocated to bytes in any obvious order at all to: It is possible that bits are not be allocated to bytes in any obvious order at all. change "are not be allocated" to "are not allocated". On page 131 lines 4249-4251 instead of making the change suggested in the Desired Action change: Such a definition would not be a proper superset of the C or POSIX locale and, thus, it might not be possible for conforming applications to work properly. to: Such a definition would not be a proper superset of the C or POSIX locale and consequently it is possible that a conforming utility or application does not behave as described in this standard.

Issue History
Date Modified	Username	Field	Change
2024-11-19 15:10	geoffclare	New Issue
2024-11-19 15:10	geoffclare	Name	=> Geoff Clare
2024-11-19 15:10	geoffclare	Organization	=> The Open Group
2024-11-19 15:10	geoffclare	Section	=> (many)
2024-11-19 15:10	geoffclare	Page Number	=> (many)
2024-11-19 15:10	geoffclare	Line Number	=> (many)
2024-11-19 15:10	geoffclare	Interp Status	=> ---
2024-11-19 22:49	Don Cragun	Note Added: 0006967
2024-11-19 22:51	Don Cragun	Note Edited: 0006967
2024-11-21 16:47	Don Cragun	Note Added: 0006968
2024-11-21 16:50	Don Cragun	Final Accepted Text	=> See Note: 0006968.
2024-11-21 16:50	Don Cragun	Status	New => Resolved
2024-11-21 16:50	Don Cragun	Resolution	Open => Accepted As Marked
2024-11-21 16:50	Don Cragun	Tag Attached: tc1-2024
2024-11-21 17:02	Don Cragun	Note Edited: 0006968

Mantis 1.1.6[^]

Copyright © 2000 - 2008 Mantis Group