3 ms·
Have you seen, for example, how he structured his code? One file per C function, with no header files. And guess what? He still does that to new code.
by dozzie 11y ago
Have you seen, for example, how he structured his code? One file per C function, with no header files. And guess what? He still does that to new code.
- dfc 11y agoOne file per C function enables an attacker to _____ qmail/djbdns/etc. ???
- marssaxman 11y agoOne file per C function is an old practice you can still see in many libc implementations and in other pieces of code designed to be used as a static library. Since a traditional Unix static library is nothing but an archive of .o files, and a traditional Unix linker makes its include-or-omit decisions on the granularity of an .o file, putting each function in a separate source file maximizes the linker's ability to strip unused functions out of a static library.
- regularfry 11y agoglibc does something similar. I'm not sure I see the problem. It's different, but I wouldn't call it bad.