|
|
| Reporter | geoffclare | Assigned To | | |
|---|
| Priority | normal | Severity | Objection | Type | Omission |
|---|
| Status | Closed | Resolution | Accepted | |
|---|
| 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 |
|---|
