bjorn 6291a5ad5a Always check malloc result; Less calloc; ... Some more questions: - Should there be some kind of allocation helper so you don't need to always check the result? - Throwing an error on OOM is convenient and is probably correct 90% of the time, it even provides a nice error message instead of a nil dereference somewhere. But it's inflexible. Is it the right thing to do?		2019-01-29 16:53:01 -08:00
..
file.c	lovrRelease frees objects instead of destructor;	2018-12-19 01:41:01 -08:00
file.h	Use naming convention for destructor;	2018-12-19 01:04:42 -08:00
filesystem.c	Always check malloc result; Less calloc;	2019-01-29 16:53:01 -08:00
filesystem.h	Revert "Replace sprintf with stb version;"	2019-01-24 17:39:27 -08:00