icon Top 9 categories map      RocketAware > man pages >

fgets(3)

Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.


The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Home

Search all pages


Subjects

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

    

RocketLink!--> Man page versions: OpenBSD FreeBSD Others

[ANSI C X3.159-1989]

FGETS(3)                  OpenBSD Programmer's Manual                 FGETS(3)

NAME
     fgets, gets - get a line from a stream



SYNOPSIS
     #include <stdio.h>

     char *
     fgets(char *str, int size, FILE *stream);

     char *
     gets(char *str);

DESCRIPTION
     The fgets() function reads at most one less than the number of characters
     specified by size from the given stream and stores them in the string
     str. Reading stops when a newline character is found, at end-of-file or
     error.  The newline, if any, is retained.  In any case a `\0' character
     is appended to end the string.

     The gets() function is equivalent to fgets() with an infinite size and a
     stream of stdin, except that the newline character (if any) is not stored
     in the string.  It is the caller's responsibility to ensure that the in-
     put line, if any, is sufficiently short to fit in the string.

RETURN VALUES
     Upon successful completion, fgets() and gets() return a pointer to the
     string.  If end-of-file or an error occurs before any characters are
     read, they return NULL. The fgets() and functions gets() do not distin-
     guish between end-of-file and error, and callers must use feof(3) and
     ferror(3) to determine which occurred.

ERRORS
     [EBADF]       The given stream is not a readable stream.

     The function fgets() may also fail and set errno for any of the errors
     specified for the routines fflush(3),  fstat(2),  read(2),  or malloc(3).


     The function gets() may also fail and set errno for any of the errors
     specified for the routine getchar(3).

CAVEATS
     The following bit of code illustrates a case where the programmer assumes
     a string is too long if it does not contain a newline:

             char buf[1024], *p;

             while (fgets(buf, sizeof(buf), fp)) {
                     if (!(p = strchr(buf, '\n')) {
                             fprintf(stderr, "input line too long.0);
                             exit(1);
                     }
                     *p = '\0';
                     printf("%s\n", p);
             }

     While the error would be true if a line > 1023 characters were read, it
     would be false in two other cases:

           1.   If the last line in a file does not contain a newline, the
                string returned by fgets() will not contain a newline either.
                Thus strchr() will return NULL and the program will terminate,

                even if the line was valid.

           2.   All C string functions, including strchr(), correctly assume
                the end of the string is represented by a null (`\0') charac-
                ter.  If the first character of a line returned by fgets()
                were null, strchr() would immediately return without consider-
                ing the rest of the returned text which may indeed include a
                newline.

     Consider using fgetln(3) instead when dealing with untrusted input.

SEE ALSO
     feof(3),  ferror(3),  fgetln(3)

STANDARDS
     The functions fgets() and gets() conform to ANSI X3.159-1989 (``ANSI
     C'').

BUGS
     Since it is usually impossible to ensure that the next input line is less
     than some arbitrary length, and because overflowing the input buffer is
     almost invariably a security violation, programs should NEVER use gets().
     The gets() function exists purely to conform to ANSI X3.159-1989 (``ANSI
     C'').

OpenBSD 2.6                      June 4, 1993                                2

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.



(Corrections, notes, and links courtesy of RocketAware.com)


[Detailed Topics]
FreeBSD Sources for fgets(3) functions
OpenBSD sources for fgets(3)


[Overview Topics]

Up to: Stdio Stream file operations - Buffered access of files and devices. fopen, fputc, fgetc, et al.


RocketLink!--> Man page versions: OpenBSD FreeBSD Others

[ANSI C X3.159-1989]




Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > fgets.3/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments