View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
00005631003.1(2008)/Issue 7Base Definitions and Headerspublic2012-05-04 16:312012-05-10 15:13
Reportermstrbill Assigned Toajosey  
PrioritynormalSeverityEditorialTypeError
Status ClosedResolutionRejected 
NameWilliam Toth
OrganizationIBM Austin
User Reference
SectionXBD - <unistd.h>
Page Numberpg 439 pdf file
Line Number14867
Interp Status---
Final Accepted Text0000563:0001235
Summary0000563: _CS_V6_ENV was not defined in SUSv3
DescriptionThe list of obsolescent symbolic constants contains _CS_V6_ENV. It was added presumably because SUSv4 requires _CS_V7_ENV to be defined. However, SUSv3 did not define _CS_V6_ENV, so it should not be included in this list.
Desired Actionremove line 14867.
TagsNo tags attached.

Activities

geoffclare

2012-05-08 08:47

manager   bugnote:0001235

I think adding _CS_V6_ENV in Issue 7 (along with _CS_V7_ENV) was
intentional. It's because the symbol originally arose in an interp
for Issue 6:

collaboration.opengroup.org/austin/interps/documents/9868/AI-047.txt

I agree that having an OB symbol "for compatibility with Issue 6"
that wasn't actually in Issue 6 is a little odd, but that's what we
decided we wanted when we were developing Issue 7.

Issue History

Date Modified Username Field Change
2012-05-04 16:31 mstrbill New Issue
2012-05-04 16:31 mstrbill Status New => Under Review
2012-05-04 16:31 mstrbill Assigned To => ajosey
2012-05-04 16:31 mstrbill Name => William Toth
2012-05-04 16:31 mstrbill Organization => IBM Austin
2012-05-04 16:31 mstrbill Section => XBD - <unistd.h>
2012-05-04 16:31 mstrbill Page Number => pg 439 pdf file
2012-05-04 16:31 mstrbill Line Number => 14867
2012-05-08 08:47 geoffclare Note Added: 0001235
2012-05-10 15:13 msbrown Interp Status => ---
2012-05-10 15:13 msbrown Final Accepted Text => 0000563:0001235
2012-05-10 15:13 msbrown Status Under Review => Closed
2012-05-10 15:13 msbrown Resolution Open => Rejected