Email List: Xaustin-group-lX
[All Lists]

[1003.1(2008)/Issue 7 0000182]: Unsafe use of LINE_MAX in fgets() exampl

To: austin-group-l@xxxxxxxxxxxxx
Subject: [1003.1(2008)/Issue 7 0000182]: Unsafe use of LINE_MAX in fgets() example
From: Austin Group Bug Tracker <noreply@xxxxxxxxxxxxx>
Date: Fri, 13 Nov 2009 10:07:39 +0000
Keywords: [1003.1(2008)/Issue 7] System Interfaces
A NOTE has been added to this issue. 
====================================================================== 
http://austingroupbugs.net/view.php?id=182 
====================================================================== 
Reported By:                Don Cragun
Assigned To:                ajosey
====================================================================== 
Project:                    1003.1(2008)/Issue 7
Issue ID:                   182
Category:                   System Interfaces
Type:                       Error
Severity:                   Comment
Priority:                   normal
Status:                     Under Review
Name:                       Don Cragun 
Organization:               Self 
User Reference:             fgets() LINE_MAX 
Section:                    fgets() EXAMPLES 
Page Number:                852 
Line Number:                28298-28308 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2009-11-12 19:23 UTC
Last Modified:              2009-11-13 10:07 UTC
====================================================================== 
Summary:                    Unsafe use of LINE_MAX in fgets() example
====================================================================== 

---------------------------------------------------------------------- 
 (0000304) geoffclare (manager) - 2009-11-13 10:07
 http://austingroupbugs.net/view.php?id=182#c304 
---------------------------------------------------------------------- 
> it is not safe to assume fgets won't be reading from stdin, i.e., a
> pipe or the keyboard. The wording should reflect that.

The wording does already reflect that.  You seem to be misreading
"file" as "regular file".  In the standard a "file" is "an object that
can be written to, or read from, or both" (see XBD7 3.164). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-12 19:23 Don Cragun     New Issue                                    
2009-11-12 19:23 Don Cragun     Status                   New => Under Review 
2009-11-12 19:23 Don Cragun     Assigned To               => ajosey          
2009-11-12 19:23 Don Cragun     Name                      => Don Cragun      
2009-11-12 19:23 Don Cragun     Organization              => Self            
2009-11-12 19:23 Don Cragun     User Reference            => fgets() LINE_MAX
2009-11-12 19:23 Don Cragun     Section                   => fgets() EXAMPLES
2009-11-12 19:23 Don Cragun     Page Number               => 852             
2009-11-12 19:23 Don Cragun     Line Number               => 28298-28308     
2009-11-12 19:23 Don Cragun     Interp Status             => ---             
2009-11-12 20:22 wpollock       Note Added: 0000302                          
2009-11-12 20:31 nsitbon        Note Added: 0000303                          
2009-11-13 10:07 geoffclare     Note Added: 0000304                          
======================================================================

<Prev in Thread] Current Thread [Next in Thread>