|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001394 |
[Issue 8 drafts] System Interfaces |
Objection |
Omission |
2020-08-26 09:18 |
2020-10-08 10:39 |
|
|
Reporter |
geoffclare |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Applied |
|
Product Version |
Draft 1 |
|
|
Name |
Geoff Clare |
|
Organization |
The Open Group |
|
User Reference |
|
|
Section |
getenv() |
|
Page Number |
1011 |
|
Line Number |
34750 |
|
Final Accepted Text |
|
|
|
Summary |
0001394: Another way the getenv() return string is modifiable |
|
Description |
Bug 0000188 added some text that acknowledges the application can modify the string returned by getenv() if it is part of a string previously added to the environment using putenv().
However, applications can also arrange for getenv() to return a known-modifiable string by setting environ to point to a suitable array of strings.
|
|
Desired Action |
Change:The application shall ensure that it does not modify the string pointed to by the getenv() function, [XSI]unless it is part of a string previously added to the environment using putenv()[/XSI]. to:The application shall ensure that it does not modify the string pointed to by the getenv() function, [CX]unless it is part of a modifiable object previously placed in the environment by assigning a new value to environ[/CX] [XSI]or by using putenv()[/XSI].
|
| Tags |
issue8 |
|
|
Attached Files |
|
|
|
Relationships 
