Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why? It has quite nice simple syntax. And all C newbies love it (doing malloc and then free is cumbersome, and not needed in simple cases).


What about lack of bounds checking leaving the door open to security exploits, in the days where CVEs caused by C's use increase every month?!?

Hence why they were dropped in C11. Being an optional annex means that actually most C vendors won't bother.


Why is that different from heap allocations? They don't have automatic bounds checking either.


Malloc does not corrupt the heap if it cannot accommodate the requested block size.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: