The first two tables list CERT C Coding Standard rules and recommendations that are Applicable in Principle, meaning that the guideline can be applied to Android app development, but examples currently shown in the guideline are not yet relevant to Android. The third table lists rules and recommendations with Unknown applicability, meaning they are guidelines whose applicability to Android app development has not yet been determined.
Contents
Rules/Applicable in Principle to Android Development
Recommendations/Applicable in Principle to Android Development
| Recommendations | Comments |
| FLP04-C. Check floating-point inputs for exceptional values | Maybe currently, a restriction on size of ints/doubles, etc. (64 bit chips) |
| FLP05-C. Do not use denormalized numbers | Maybe currently, a restriction on size of ints/doubles, etc. (64 bit chips) |
| FLP06-C. Convert integers to floating point for floating-point operations | Maybe currently, a restriction on size of ints/doubles, etc. (64 bit chips) |
| FLP07-C. Cast the return value of a function that returns a floating-point type | Maybe currently, a restriction on size of ints/doubles, etc. (64 bit chips) |
| STR11-C. Do not specify the bound of a character array initialized with a string literal | Arrays: Need examination of Android support. (gcc support of arrays partial). Note native code array issues different with ART than with Dalvik: http://developer.android.com/guide/practices/verifying-apps-art.html#JNI_Issues |
| SIG00-C. Mask signals handled by noninterruptible signal handlers | SigAction may solve these problems. If Android supports SigAction, these rules/recommendations may not be needed. http://stackoverflow.com/questions/7245550/android-app-restarts-automatically-after-a-crash |
| SIG01-C. Understand implementation-specific details regarding signal handler persistence | SigAction may solve these problems. If Android supports SigAction, these rules/recommendations may not be needed. http://stackoverflow.com/questions/7245550/android-app-restarts-automatically-after-a-crash |
| SIG02-C. Avoid using signals to implement normal functionality | SigAction may solve these problems. If Android supports SigAction, these rules/recommendations may not be needed. http://stackoverflow.com/questions/7245550/android-app-restarts-automatically-after-a-crash |
| API02-C. Functions that read or write to or from an array should take an argument to specify the source or target size | Arrays: Need examination of Android support. (gcc support of arrays partial). Note native code array issues different with ART than with Dalvik: http://developer.android.com/guide/practices/verifying-apps-art.html#JNI_Issues |
| API05-C. Use conformant array parameters | Arrays: Need examination of Android support. (gcc support of arrays partial). Note native code array issues different with ART than with Dalvik: http://developer.android.com/guide/practices/verifying-apps-art.html#JNI_Issues |
| MSC19-C. For functions that return an array, prefer returning an empty array over a null value | Arrays: Need examination of Android support. (gcc support of arrays partial). Note native code array issues different with ART than with Dalvik: http://developer.android.com/guide/practices/verifying-apps-art.html#JNI_Issues |