checking for NULL before calling free

by

The construct:

free(NULL);

has always been OK in C, back to the original UNIX compiler written by Dennis Ritchie. Pre-standardisation, some poor compilers might not have fielded it correctly, but these days any compiler that does not cannot legitimately call itself a compiler for the C language. Using it typically leads to clearer, more maintainable code.

More Related Contents:

  1. Getting a stack overflow exception when declaring a large array
  2. Why is the use of alloca() not considered good practice?
  3. Determine size of dynamically allocated memory in C
  4. Allocate memory 2d array in function C
  5. Freaky way of allocating two-dimensional array?
  6. Why does the compiler allocate more than needed in the stack?
  7. malloc(sizeof(int)) vs malloc(sizeof(int *)) vs (int *)malloc(sizeof(int))
  8. Should I check if malloc() was successful?
  9. Is it possible to allocate array inside function and return it using reference?
  10. dynamic allocating array of arrays in C
  11. How to avoid long chain of free’s (or deletes) after every error check in C?
  12. Thread for Background Music
  13. Access element of array of pointer of structure
  14. pointer to string concept in c [closed]
  15. my code does not work and I don’t know why ;-;
  16. Pointer subtraction confusion
  17. Difference between a Structure and a Union
  18. Why does this implementation of offsetof() work?
  19. Concatenating Variable Names in C?
  20. C Program crashes when adding an extra int
  21. How to get fractions in an integer division?
  22. How to print the address of a function?
  23. What does the statement if (counter & (1
  24. When can argv[0] have null?
  25. How to trap unaligned memory access?
  26. Empty structure in C
  27. Unexpected C/C++ bitwise shift operators outcome
  28. faster alternative to memcpy?
  29. log2 not found in my math.h?
  30. An interesting C linked list idiom

Leave a Comment