FreeEMS Issues - Firmware | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000191 | Firmware | Structure / Style | public | 2011-06-28 10:30 | 2011-06-28 10:30 |
| Reporter | Fred | ||||
| Assigned To | Fred | ||||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | ASAP | Fixed in Version | |||
| FirmwareVersion | |||||
| Issue Type | Task | ||||
| Risk of Breakage | very low | ||||
| Summary | 0000191: Formalise Code Style | ||||
| Description | For others to contribute in a low impact way, and leave the source looking and feeling good, the firmware source style must be formalised, and an automated formatter (for eclipse perhaps) should be included, if possible. The latter requirement may require some change in how certain structures are currently formatted. | ||||
| Steps To Reproduce | |||||
| Additional Information | Some worthwhile reading on the subject: http://www.kernel.org/doc/Documentation/CodingStyle [^] http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/ [^] Some of the above is absolutely not making it in, but some of it is right on target! | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| There are no notes attached to this issue. |