====== Programming Style Guide ======
[[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]]

A **Programming Style Guide**, also known as **Programming Style**, **Style Guide**, or **Code Style**, is a set of rules or guidelines used when writing the source code for a computer program. It is often claimed that following a particular programming style will help programmers read and understand source code conforming to the style, and help to avoid introducing errors.

**Programming Styles Guides** are generally designed for a specific programming language (or language family, such as C/C+). For example, a style considered good in C source code may not be appropriate for BASIC source code, etc. However, some rules are commonly applied to many languages (C/C+,Java, C#, Rust, etc.).

Source: [[https://en.wikipedia.org/wiki/Programming_style ]]

Widely accepted style guides are ((
[[https://www.pullrequest.com/blog/create-a-programming-style-guide/]]
)):

  * [[https://github.com/google/styleguide | Google’s Style Guides]]
  * [[https://github.com/standard/standard | JavaScript Standard Style]]
  * [[https://github.com/github/rubocop-github/blob/master/STYLEGUIDE.md | GitHub’s Ruby Style Guide]]
  * [[https://www.python.org/dev/peps/pep-0008/? | Python Foundation’s Style Guide]]
  * [[https://github.com/airbnb/javascript | Airbnb’s JavaScript Style Guide]]
  * [[https://angular.io/guide/styleguide | Angular’s Style Guide]]
  : **Note:** There is an exception list of Coding Styles compiled by Wahyu Kristianto  at [[https://github.com/Kristories/awesome-guidelines | Awesome Guidelines]]


/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~