Do you know that? 15% American freelancers earn $100+/hr next

Is it better to use malloc() or calloc()?

Both the malloc() and the calloc() functions are used to allocate dynamic memory. Each operates slightly
different from the other. malloc() takes a size and returns a pointer to a chunk of memory at least that big:

void    *malloc( size_t size );

calloc() takes a number of elements, and the size of each, and returns a pointer to a chunk of memory at
least big enough to hold them all:

void    *calloc( size_t numElements, size_t sizeOfElement );

There's one major difference and one minor difference between the two functions. The major difference is
that malloc() doesn't initialize the allocated memory. The first time malloc() gives you a particular chunk
of memory, the memory might be full of zeros. If memory has been allocated, freed, and reallocated, it
probably has whatever junk was left in it. That means, unfortunately, that a program might run in simple
cases (when memory is never reallocated) but break when used harder (and when memory is reused).

calloc() fills the allocated memory with all zero bits. That means that anything there you're going to use
as a char or an int of any length, signed or unsigned, is guaranteed to be zero. Anything you're going to use
as a pointer is set to all zero bits. That's usually a null pointer, but it's not guaranteed.

Anything you're going to use as a float or double is set to all zero bits; that's a floating-point zero on some
types of machines, but not on all.

The minor difference between the two is that calloc() returns an array of objects; malloc() returns one
object. Some people use calloc() to make clear that they want an array. Other than initialization, most C
programmers don't distinguish between

calloc( numElements, sizeOfElement)

and

malloc( numElements * sizeOfElement)

There's a nit, though. malloc() doesn't give you a pointer to an array. In theory (according to the ANSI C
standard), pointer arithmetic works only within a single array. In practice, if any C compiler or interpreter
were to enforce that theory, lots of existing C code would break. (There wouldn't be much use for realloc(),
either, which also doesn't guarantee a pointer to an array.)

Don't worry about the array-ness of calloc(). If you want initialization to zeros, use calloc(); if not, use malloc().