Austin Group Defect Tracker

Aardvark Mark IV

Main | My View | View Issues | Change Log | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ Issue History ] [ Print ]
ID Category Severity Type Date Submitted Last Update
0000587 [1003.1(2008)/Issue 7] System Interfaces Objection Omission 2012-06-25 15:39 2019-06-10 08:55
Reporter geoffclare View Status public  
Assigned To ajosey
Priority normal Resolution Accepted  
Status Closed  
Name Geoff Clare
Organization The Open Group
User Reference
Section fmemopen
Page Number 866
Line Number 28765
Interp Status Approved
Final Accepted Text See Note: 0001275
Summary 0000587: fmemopen() initial buffer size for null pointer case
Description The fmemopen() description does not specify the initial buffer
size for the case where an append mode is used and the buf argument
is a null pointer.
Desired Action Change:

    for modes a and a+ the initial size shall be either the position
    of the first null byte in the buffer or the value of the size
    argument if no null byte is found

to:

    for modes a and a+ the initial size shall be:

    * zero, if buf is a null pointer
    * the position of the first null byte in the buffer, if one is found
    * the value of the size argument, if buf is not a null pointer and no
      null byte is found
Tags tc2-2008
Attached Files

- Relationships
related to 0000818Closed 1003.1(2013)/Issue7+TC1 fmemopen should allow 0-size buffer 

-  Notes
(0001275)
nick (manager)
2012-06-28 16:24

 Interpretation response
------------------------

The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale:
-------------
The standard does not speak to the null pointer case, but existing practice handles this case consistently.

Notes to the Editor (not part of this interpretation):
-----------------------------------------------------
See Desired Action
(0001281)
ajosey (manager)
2012-06-29 16:12
edited on: 2012-06-29 16:13

 Interpretation proposed 29 June 2012 for final 45 day review
(0001344)
ajosey (manager)
2012-08-30 09:12

 Interpretation approved 30 Aug 2012

- Issue History
Date Modified Username Field Change
2012-06-25 15:39 geoffclare New Issue
2012-06-25 15:39 geoffclare Status New => Under Review
2012-06-25 15:39 geoffclare Assigned To => ajosey
2012-06-25 15:39 geoffclare Name => Geoff Clare
2012-06-25 15:39 geoffclare Organization => The Open Group
2012-06-25 15:39 geoffclare Section => fmemopen
2012-06-25 15:39 geoffclare Page Number => 866
2012-06-25 15:39 geoffclare Line Number => 28765
2012-06-25 15:39 geoffclare Interp Status => ---
2012-06-28 16:24 nick Interp Status --- => Pending
2012-06-28 16:24 nick Note Added: 0001275
2012-06-28 16:24 nick Status Under Review => Interpretation Required
2012-06-28 16:24 nick Resolution Open => Accepted
2012-06-28 16:24 nick Final Accepted Text => See Note: 0001275
2012-06-28 16:24 nick Tag Attached: tc2-2008
2012-06-29 16:12 ajosey Interp Status Pending => Proposed
2012-06-29 16:12 ajosey Note Added: 0001281
2012-06-29 16:13 ajosey Note Edited: 0001281
2012-08-30 09:12 ajosey Interp Status Proposed => Approved
2012-08-30 09:12 ajosey Note Added: 0001344
2014-01-30 04:06 eblake Relationship added related to 0000818
2019-06-10 08:55 agadmin Status Interpretation Required => Closed

Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker