3 ms·
in C I always end up building my own world because the default one is broken. for example null terminated strings are just really awful to work with. i'm not al
by convolvatron 5y ago
in C I always end up building my own world because the default one is broken. for example null terminated strings are just really awful to work with. i'm not alone - alot of larger C projects have their own runtime, particularly memory management. another cross-cutting concern is multihreaded safety and scheduling.
unless the library author broke those functions out, then I need to rehost it in my environment. so I usually end up forking any library that I want to use. this isn't all bad - I find some bugs and integrate the build. I adopt the library and develop and understanding of it sufficient to maintain it myself.
contrast that to a language environment where those things - strings and threads and build are all standardized.
- mgaunard 5y agoMy point of view is that if you program in C you most likely care about being in control of what happens. Your approach makes perfect sense within that context.