dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: C++
Expertise: Beginner
Apr 4, 2000

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Tackling a Common Bug With scanf()

In legacy code and environments that support C exclusively, using scanf() is still a widespread method of getting input from a user (or a file, when using fscanf()). When using this function, beware of a common bug that results from C's weak type-checking:

 
  #include <stdio.h>
  int main()
  {
    int n;
    scanf("%d", n); /* a bug; should read '&n' */
  }

The first parameter of scanf() is a format string that describes the type and length of the data to be read. The following arguments must be one ore more pointers to buffers into which the input is written. Unlike C++, C enforces weak type checks. Therefore, a C compiler doesn't detect that the second argument passed to scanf() is an int rather than a pointer to int. Consequently, the program's behavior is undefined—the input is written to a random memory address, not to n. The correct form should be:

 
  scanf("%d", &n); /* now OK */
Danny Kalev
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date