A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1858 
====================================================================== 
Reported By:                nabijaczleweli
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1858
Category:                   System Interfaces
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     Interpretation Required
Name:                       наб 
Organization:                
User Reference:              
Section:                    open_memstream 
Page Number:                1526 
Line Number:                51164-51176 
Interp Status:              Pending 
Final Accepted Text:        https://austingroupbugs.net/view.php?id=1858#c6901 
====================================================================== 
Date Submitted:             2024-09-19 12:25 UTC
Last Modified:              2024-10-03 15:51 UTC
====================================================================== 
Summary:                    open_memstream() doesn't say where the result lies
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001406 clarification of SEEK_END when current ...
====================================================================== 

---------------------------------------------------------------------- 
 (0006902) geoffclare (manager) - 2024-10-03 15:51
 https://austingroupbugs.net/view.php?id=1858#c6902 
---------------------------------------------------------------------- 
Changing the test program from the bug description to use fflush() instead
of fclose() produces the output "gamingQereftalan" with glibc. Because of
this difference in behavior between fflush() and fclose() this is
considered to be a bug/misfeature of fclose() in glibc. The standard is
clear that the effect of these two functions on buffer contents must be the
same. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-09-19 12:25 nabijaczleweli New Issue                                    
2024-09-19 12:25 nabijaczleweli Name                      => наб          
2024-09-19 12:25 nabijaczleweli Section                   => open_memstream  
2024-09-19 12:25 nabijaczleweli Page Number               => 1526            
2024-09-19 12:25 nabijaczleweli Line Number               => 51164-51176     
2024-09-26 13:45 geoffclare     Relationship added       related to 0001406  
2024-09-26 17:09 Florian Weimer Issue Monitored: Florian Weimer                 
  
2024-10-03 15:48 geoffclare     Note Added: 0006901                          
2024-10-03 15:50 geoffclare     Interp Status             => Pending         
2024-10-03 15:50 geoffclare     Final Accepted Text       =>
https://austingroupbugs.net/view.php?id=1858#c6901    
2024-10-03 15:50 geoffclare     Status                   New => Interpretation
Required
2024-10-03 15:50 geoffclare     Resolution               Open => Accepted As
Marked
2024-10-03 15:51 geoffclare     Note Added: 0006902                          
======================================================================


  • [1003.1(2024... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to