[TIMOB-8627] iOS: Refine Obj-C, Obj-C++ coding standards
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-04-20T13:34:15.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 2.1.0, Sprint 2012-08 |
| Components | iOS |
| Labels | core |
| Reporter | Ingo Muschenetz |
| Assignee | Ingo Muschenetz |
| Created | 2012-04-09T14:41:41.000+0000 |
| Updated | 2014-02-04T01:09:20.000+0000 |
Description
iOS currently has some [coding standards](https://wiki.appcelerator.org/display/pe/Coding+Standards) available, with an uncrustify (to beautify source) in [tidevtools](https://github.com/billdawson/tidevtools). We need to evaluate the uncrustify (and manually written instructions) for:
* Correctness
* Completeness
* Consistency
* Tabs vs. spaces (we need to standardize on one!)
These standards should apply to Objective-C and Objective-C++ only, but may require some preliminary drafts for C and C++ style. This ticket is *not* for establishing design patterns or workflow (unlike the broad scope of TIMOB-8241, which is being narrowed.)
Part of this ticket is also deciding how to enforce code formatting (i.e. coerce all submitters to make their source conform to the standard).
Updated the uncrustify: https://github.com/billdawson/tidevtools/blob/master/uncrustify_objc.cfg
[Objective-C(++) standards on the wiki.](https://wiki.appcelerator.org/pages/viewpage.action?pageId=30088343)
Not locking this down until we've resolved C/C++ Standards (TIMOB-8681) as I expect the Obj-C(\+\+) standard to be built on top of those to a degree. The initial work on the Obj-C standard is expected to inform the C/C\+\+ standard however.
Moving to next Core sprint.
By unanimous consent of the core group, this ticket is resolved now; the C and C++ standards will only introduce minor changes and the current C/C++ guidelines in the Obj-C standards are considered to be a baseline for starting our C/C++ standards.