Difference between revisions of "Coding style"
Jump to navigation
Jump to search
(Create new local page for notes on code style and best practices.) |
m (Add link to Linux Kernel coding style documentation.) |
||
| Line 16: | Line 16: | ||
* https://github.com/apache/httpd/blob/trunk/server/util_mutex.c#L134 | * https://github.com/apache/httpd/blob/trunk/server/util_mutex.c#L134 | ||
| + | |||
| + | Linux Kernel coding style: | ||
| + | |||
| + | * https://docs.kernel.org/process/coding-style.html | ||
| + | |||
| + | <!-- odne komentar --> | ||
Latest revision as of 21:17, 7 August 2025
Coding Style Notes
Some starting references. First links here gathered to answer question "How do big projects style their code and practices?"
Apache2 webserver hosts their project on github. They have an area of their project named "modules", and there is an example module provided for developers wanting to learn how to use Apache2 API: . . .
Question to look further into, how do professional established coding teams name their variables? How do they name enumeration instances?
Linux Kernel coding style: