Update
This commit is contained in:
parent
8b530b5952
commit
64fd120266
35 changed files with 2034 additions and 2007 deletions
|
@ -2,7 +2,7 @@
|
|||
|
||||
Probably in majority of cases a [programming language](programming_language.md) lets the programmer choose the aesthetic style in which to write the code (just like a writer may format his text in visually different ways without changing the meaning of it) -- one has a choice in naming variables, indentation and aligning commands, inserting [comments](comment.md) and so on. This gives rise to various styles -- typically a programmer will have his own preferred style, kind of like handwriting, but once he works in a team, some compromise has to be found to which everyone must conform so as to keep the code nice, consistent and [readable](readability.md) by everyone. Some project, e.g. [Linux](linux.md), have evolved quite good, tested and de facto standardized styles, so instead of inventing a custom style (which may not be as easy as it sounds) one may choose to adopt some of the existing styles. While this is more of a surface-level part of programming, it is still quite important and thinking about it may go very deep, it is not to be underestimated.
|
||||
|
||||
There exist automatic code formatters, they are often called **code beautifiers**. But not everything can be automatized, for example a program will hardly comment your code, or inserting empty spaces to separate logically related parts of a sequential code is also something that human like intelligence is needed for.
|
||||
There exist automatic code formatters, they are often called **code beautifiers**. But not everything can be automated, for example a program will hardly comment your code, or inserting empty spaces to separate logically related parts of a sequential code is also something that human like intelligence is needed for.
|
||||
|
||||
## Recommended LRS C Programming Style/Formatting
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue