Why does C++ require a cast for malloc() but C doesn’t?

by

Several points:

C allows void pointers to be implicitly converted to any other object pointer type. C++ does not.

Casting the result of malloc() in C will supress a useful diagnostic if you forget to include stdlib.h or otherwise don’t have a declaration for malloc() in scope. Remember that if C sees a function call without a prior declaration, it will assume that the function returns int. If you don’t have a declaration for malloc() and you leave off the cast, you’ll get a diagnostic to the effect that you’re trying to assign incompatible types (int to pointer). If you cast the result, you supress the diagnostic and will potentially have runtime issues, since it’s not guaranteed that converting a pointer value to an int and back to a pointer again will give you a useful result.

If you’re writing C++, you should be using new and delete instead of malloc() and free(). Yeah, yeah, yeah, I’ve heard all the reasons why people want their code to compile as both C and C++, but the benefits of using the right memory management tool for the language outweigh the cost of maintaining two versions IMO.

Note: the void * type was added in the C89 standard; earlier versions of C had malloc() return char *, so in those versions the cast was required if you were assigning the result to a different pointer type. Almost everybody supports at least the C89 standard though, so the odds of you running into one of those older implementations is very, very low.

More Related Contents:

  1. convert static_castmalloc/free to new/delete
  2. convert malloc to new c++ for struct
  3. In what cases do I use malloc and/or new?
  4. How do malloc() and free() work?
  5. How to use a C++ string in a structure when malloc()-ing the same structure?
  6. invalid conversion from `void*’ to `char*’ when using malloc?
  7. What is the difference between “new” and “malloc” and “calloc” in C++? [duplicate]
  8. How can I get the size of a memory block allocated using malloc()? [duplicate]
  9. Check if a pointer points to allocated memory on the heap
  10. write and read string to binary file C++
  11. Is circumventing a class’ constructor legal or does it result in undefined behaviour?
  12. Why is it that we can write outside of bounds in C?
  13. Multithreaded Memory Allocators for C/C++
  14. Behaviour of malloc with delete in C++
  15. dynamically allocated memory after program termination
  16. How to alloc a executable memory buffer?
  17. Memory allocation and deallocation across dll boundaries
  18. malloc() vs. HeapAlloc()
  19. Segfaults in malloc() and malloc_consolidate()
  20. Can you allocate a very large single chunk of memory ( > 4GB ) in c or c++?
  21. new, delete ,malloc & free
  22. How can I store a value at a specific location in the memory?
  23. What is C++ version of realloc(), to allocate the new buffer and copy the contents from the old one?
  24. sizeof works unusual at c++ after array creation [duplicate]
  25. How can I read and parse CSV files in C++?
  26. Can I set a breakpoint on ‘memory access’ in GDB?
  27. What’s this C++ syntax that puts a brace-surrounded block where an expression is expected?
  28. Generate SHA hash in C++ using OpenSSL library
  29. use std::fill to populate vector with increasing numbers
  30. Can Google Mock a method with a smart pointer return type?

Leave a Comment