| Anonymous | Login | Signup for a new account | 2010-09-08 04:54 UTC |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0000010 | [Firmware] Structure / Style | minor | N/A | 2008-10-29 16:28 | 2009-01-02 14:57 | ||
| Reporter | Fred | View Status | public | ||||
| Assigned To | Fred | ||||||
| Priority | low | Resolution | fixed | ||||
| Status | closed | Product Version | |||||
| Summary | 0000010: Document And Standardise Upon Coding Conventions | ||||||
| Description |
Currently the coding style is only consistent within modules. Inter module it has some inconsistencies that aren't serious, but should be fixed. We need to define formal coding conventions and then format all the code and adjust all the variables to be in line with that style. Some examples of things that need to be defined are : * Case, upper, lower, camel, leading upper on camel or not, etc. This needs to be done for each class of identifier. eg defined constants, const constants, local vars, global vars, function names, etc * tabs/spaces/length of tabs, locations of braces, spaces between if( or if ( blank lines between block of code, etc * file naming conventions similar to identifiers * comments, size, type, location, chars to EOL etc * GNU GPL header MUST be in place before release * Some specific prefixes standardised upon for identifiers related to certain modules etc * header structure standard - needs to be defined, see related task * where multiple terms exist for a single thing, define which to use Probably other things, suggestions on the above and additional things most welcome. |
||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Issue Type | Improvement | ||||||
| Attached Files | |||||||
|
|
|||||||
| Mantis 1.1.7[^] Copyright © 2000 - 2008 Mantis Group |