3 ms·
Well, the bug only appears if you didn't include the header file declaring malloc (or any other void*-returning function). If you did, there's no problem. It'
by nostrademons 14y ago
Well, the bug only appears if you didn't include the header file declaring malloc (or any other void*-returning function). If you did, there's no problem.
It's a pretty easy thing to leave out, missing a required header, but if you always compile under -Wall it'll catch this and many other problems as well.
- graycat 14y agoThanks for the details, but I remain concerned about taking a language, clearly with some tricky aspects, so closely identified with 16 and 32 bit computing into 64 bit computing.