Coding standards for all Yzena projects
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Gavin Howard 46fb6bff6e
Update the license
6 months ago
C Tweak C templates 1 year ago
CMake Clarify that trailing whitespace is not allowed 4 years ago
.gitconfig Add common standards 4 years ago Update the license 6 months ago Move Yzena projects away from GitHub 2 years ago Revert "Add a Code of Conduct (just copied from LambdaConf)" 4 years ago Add a TODO 1 year ago Make script executable 4 years ago

Yzena Coding Standards

WARNING: This project has moved to for these reasons.

This repo contains documents that lay out the coding standards for all Yzena projects. The documents are split by language. All submitted work must follow all of the applicable coding standards.

These standards are mandatory, even if a contributor does not agree with them. In fact, even the founder of Yzena, Gavin D. Howard, does not like all of the style because some decisions were made to make it easy to automate style formatting with clang-format. Regardless, the coding standards are there to make each repository consistent with every other, which will prevent bugs.