A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=713 
====================================================================== 
Reported By:                nsz
Assigned To:                
====================================================================== 
Project:                    1003.1(2013)/Issue7+TC1
Issue ID:                   713
Category:                   System Interfaces
Type:                       Omission
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Szabolcs Nagy 
Organization:               musl 
User Reference:              
Section:                    remquo 
Page Number:                 
Line Number:                 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2013-06-18 00:00 UTC
Last Modified:              2021-06-16 18:25 UTC
====================================================================== 
Summary:                    in remquo quo should be unspecified when the result
is NaN
====================================================================== 

---------------------------------------------------------------------- 
 (0005381) shware_systems (reporter) - 2021-06-16 18:25
 https://austingroupbugs.net/view.php?id=713#c5381 
---------------------------------------------------------------------- 
As this discussion is happening because the existing practice does not show
a clear consensus on what value they store in &quo when NaN is the function
result, I think it is in scope fpr the standard to act as referee and be
inventive. To this end, as behavior end users can rely upon, I suggest tbe
conforming behavior be, under Return Value:

If the function is to return a NaN as result value, signalling or quiet,
the value zero (0) shall be stored in &quo.

I realize this is arbitrary, could use 1, INT_MIN or INT_MAX too, but until
integer MaNs are required to be supported this is the cleanest resolution I
see. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2013-06-18 00:00 nsz            New Issue                                    
2013-06-18 00:00 nsz            Name                      => Szabolcs Nagy   
2013-06-18 00:00 nsz            Organization              => musl            
2013-06-18 00:00 nsz            Section                   => remquo          
2013-06-20 15:54 nick           Tag Attached: c99                            
2021-04-14 15:01 nick           Note Added: 0005312                          
2021-04-14 15:23 kre            Note Added: 0005313                          
2021-04-14 15:28 kre            Note Added: 0005314                          
2021-04-15 09:08 geoffclare     Note Added: 0005317                          
2021-04-15 19:58 kre            Note Added: 0005319                          
2021-04-15 19:58 kre            Note Deleted: 0005313                        
2021-04-15 19:59 kre            Note Edited: 0005319                         
2021-06-16 00:40 nick           Note Added: 0005379                          
2021-06-16 08:17 Vincent LefevreNote Added: 0005380                          
2021-06-16 18:25 shware_systems Note Added: 0005381                          
======================================================================


  • [1003.1(2013... 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
    • [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
      • Re:... Fred J. Tydeman via austin-group-l at The Open Group
      • tv_... Fred J. Tydeman via austin-group-l at The Open Group
        • ... Geoff Clare via austin-group-l at The Open Group
          • ... Fred J. Tydeman via austin-group-l at The Open Group
            • ... Geoff Clare via austin-group-l at The Open Group
              • ... Nick Stoughton via austin-group-l at The Open Group
                • ... Geoff Clare via austin-group-l at The Open Group

Reply via email to