Why not using new form of C compatibility headers ?

[zhanyuzhang]

There are many C compatibility headers in the project , for example:

#include <assert.h> // for assert
#include <stddef.h> // for NULL
#include <stdlib.h> // for malloc,realloc,free
#include <string.h> // for memset,memmov

I'm confused why not using c prefix header, as follows :

#include <cassert> // for assert
#include <cstddef> // for NULL
#include <cstdlib> // for malloc,realloc,free
#include <cstring> // for memset,memmov

I'm a new c++ beginer , and I learn that we should use the second form， beacuse the xx.h is deprecated:

referece to: https://en.cppreference.com/w/cpp/header

[ithewei]

<string.h> is c header, <cstring> is c++ header of using namespace std.
libhv base,event modules writen by c. Use c header is more compatible.