[TIMOB-8630] iOS: Refine and document Obj-C, Obj-C++ engineering patterns/design
GitHub Issue | n/a |
---|---|
Type | Story |
Priority | Low |
Status | Open |
Resolution | Unresolved |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | iOS |
Labels | core |
Reporter | Ingo Muschenetz |
Assignee | Unknown |
Created | 2012-04-09T14:55:45.000+0000 |
Updated | 2018-02-28T20:03:38.000+0000 |
Description
iOS currently has some existing [common engineering practices](https://wiki.appcelerator.org/display/pe/Coding+Standards) and ["best practices"](https://wiki.appcelerator.org/display/pe/iOS+best+practices). While these don't need to be strictly enforced, we should evaluate the existing documents for:
* Completeness
* Correctness
* Sensibility
* Langage-specific engineering questions (i.e. "pure virtual" in Obj-C, subclass vs. protocol, protocol/subclass vs. delegate, "private" method naming, etc.)
In addition this ticket should be collaborative with TIMOB-8241 to begin to establish any cross-language engineering concerns about class naming, data separation, design, etc. (especially since C and C++ standards will affect both projects).
This ticket is related to, but not dependent of, TIMOB-8627. They can be worked on concurrently although some cross-ticket pollination is expected.