Notes |
(0004470)
shware_systems (reporter)
2019-07-03 16:22
|
I believe it is UP shaded because embedded systems may not maintain a getpwnam() file, and take advantage of the unspecified behavior allowance of HOME being unset to replace the tilde with an arbitrary absolute path constant. Systems conforming to the UP option are required to maintain that file, I believe, so a valid value for HOME is always plausible and shouldn't be unset, or even a null string. |
|
(0004471)
geoffclare (manager)
2019-07-04 08:10
|
Looking at the history, it seems that this was an editorial mistake when merging POSIX.2-1992 into SUSv2 to make POSIX.1-2001/SUSv3. The text "This volume of IEEE Std 1003.1-2001 specifies the effects of this variable only for systems supporting the User Portability Utilities option" was added to FCEDIT, HISTFILE and HOME but should have been added to FCEDIT, HISTFILE and HISTSIZE (to match POSIX.2-1992).
The fix should be to remove UP shading from HOME and add it to HISTSIZE. |
|
(0004472)
shware_systems (reporter)
2019-07-04 14:15
|
Perhaps, but I think my analysis has some validity too, in that its presence is optional, so if the shading is removed it may desirable to add text accenting that aspect, e.g. Change last sentence to:
The contents of HOME, when it is set and is a non-null value, are
used in tilde expansion as described in [xref to XCU 2.6.1]. |
|