Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why does Erlang have a C NIF drop-in replacement for malloc, enif_alloc, but not calloc? Thereby forcing one to use memset() after enif_alloc for array access.
Well, I assume this has to do with the fact (from documentation):
“NIFs where introduced in R13B03 as an experimental feature.”
On a side note, the Erlang review board is also quite conservative, probably due to the history of being born from a telelcom company, and that is understandable for fault tolerant languages.
I guess I don’t see the problem you have since you are always welcome to write a proper port using calloc() and use the old marshaling methods.
http://www.erlang.org/doc/tutorial/erl_interface.html
Happy C coding!