Safe line input in C: Between fgets() and gets(), which function is considered safe for reading a line of text (and why)?

Introduction / Context:Reading entire lines including spaces is a common need in C. Historically, gets was used, but it became notorious for buffer overflow vulnerabilities and has been removed from the C standard. Knowing the safe alternative is essential for writing robust, secure C programs.

Given Data / Assumptions:

• We need to read a whole line that may contain spaces.
• We want a function that prevents buffer overflows by respecting buffer size.
• Portable, standard C behavior is desired.

Concept / Approach:

• fgets(buffer, size, stream) reads at most size-1 characters and always terminates with a null byte if any characters are read, preventing overflows.
• gets reads until newline with no size limit; it cannot prevent writing past the end of the buffer.
• Some libraries offer getline or gets_s, but these are not universally portable in the same way as fgets.

Step-by-Step Solution:

Verification / Alternative check:

Why Other Options Are Wrong:

• gets(): Dangerous and removed from the standard; it cannot limit input length.
• getline(): Useful but POSIX, not ISO C; availability varies.
• gets_s(): Bounds-checked but not portable across all environments; not ISO C90/C99.

Common Pitfalls:

• Forgetting that fgets keeps the trailing newline; trim it if needed.
• Passing the wrong size to fgets (must be the buffer's capacity).

Final Answer: