|
|
| Reporter | geoffclare | Assigned To | | |
|---|
| Priority | normal | Severity | Objection | Type | Error |
|---|
| Status | Resolved | Resolution | Accepted As Marked | |
|---|
|
|
| Name | Geoff Clare |
|---|
| Organization | The Open Group |
|---|
| User Reference | |
|---|
| Section | symlink() |
|---|
| Page Number | 2095 |
|---|
| Line Number | 67093 |
|---|
| Interp Status | --- |
|---|
| Final Accepted Text | See 0001829:0006791. |
|---|
|
|
|
|
| Summary | 0001829: symlink() and terminating null bytes |
|---|
| Description | The description of symlink() says the created symbolic link contains "the string pointed to by path1". Since a string by definition has a terminating null byte, by a strict reading this implies the null is included in the symbolic link, but that's not the intended requirement, nor how systems behave.
|
|---|
| Desired Action | On page 2095 line 67093 section symlink(), change:The symlink() function shall create a symbolic link called path2 that contains the string pointed to by path1 (path2 is the name of the symbolic link created, path1 is the string contained in the symbolic link). to:The symlink() function shall create a symbolic link called path2 that contains the string pointed to by path1, excluding the terminating null byte. (That is, path2 specifies the pathname of the symbolic link created; path1 specifies the contents of the symbolic link.)
|
|---|
| Tags | tc1-2024 |
|---|
