5 ms·
the build process of C is one of its absolute benefits. Each unit compiles on its own, producing an object file. The fact that people have now started to make h
by futharkshill 5y ago
the build process of C is one of its absolute benefits. Each unit compiles on its own, producing an object file. The fact that people have now started to make header-only libraries makes the story even better! Each function gets a name. No namespaces, classes, scopes, modules, w/e. You can even just declare a function as extern at compile time!
- Too 5y agoCan’t tell if this is sarcasm or not.
- dottedmag 5y agoC compilation is not that bad, what makes it atrocious is the preprocessing step. Show me the large-ish (100K+ LOC) codebase with dependencies that can be cross-compiled, does not come with tons of cruft like autoconf or Meson, and does not require installing reams of software on the host as "libraries", and then we are talking. (edited: typo)
- futharkshill 5y agoWhile a programming language and ecosystem includes some of the culture, bad code and project structure IMO should not be blamed on C. Modern C projects are a breeze
- dottedmag 5y ago> Modern C projects are a breeze So, where's the link to a modern C project that is a breeze to work with? Requirements are in the parent comment.
- naasking 5y agoThe fact that people have to resort to header only libraries is a sign of how bad building portable C libraries really is.