/ Build Apps

Complexity Standards

Cyclomatic Complexity

Cyclomatic complexity is a measurement of the complexity of code within a function. It is measured by counting branches within a function. Each function gets a starting value of 1, and 1 is added for every "if" (or "?"), every loop (for, do, or while), and every "case". For example, the following code has a cyclomatic complexity of 3:

Fan-Out

Fan-out is a measurement of the number of different functions that are called by a given function, plus the number of data structures that it updates. High levels of fan-out are indicative of insufficient abstraction and are correlated with higher defect density.

For example, the following function has a fan-out of 5:

staticint Log(int value)

{

if (IsAboveThreshold(value))

{

LogEntry_t* entryPtr = AllocEntry();

if (entryPtr == NULL)

{

ReportError("Out of memory!");

}

else

{

entryPtr->value = value;

entryPtr->timestamp = GetTimestamp();

// Add the entry to the log entry list.

LogEntryList[NextEntryIndex++] = entryPtr;

if (NextExtryIndex >= LOG_SIZE)

{

NextEntryIndex = 0; // wrap around

}

if (NextEntryIndex == LastEntryIndex)

{

ReportError("Log overflow! Log entry discarded.");

LastEntryIndex = (LastEntryIndex + 1) % LOG_SIZE;

}

}

}

}

The functions IsAboveThreshold(), AllocEntry(), ReportError(), and GetTimestamp() are called by the Log() function. In addition, the "Log" data structure (consisting of the variables LogEntryList, NextEntryIndex, and LastEntryIndex) is updated by the Log() function. Note that the second and subsequent calls to the same function are not counted. So, even though ReportError() is called twice by Log(), it only contributes 1 to the fan-out. Ideally, fan-out should be kept to 7 or less. Fan-out must be kept to 10 or less.

Recursion

Recursion can be dangerous because it can result in stack overruns. Don't use recursion, unless you can clearly highlight the recursion and prove to the reader of your code that the recursion will be bounded well within the limits of even the smallest stack space that could reasonably be allocated to your thread.

Gotos

"goto" statements should not be used. If they are used, they must be used sparingly as a jump-to-exception-handling mechanism.

{

Rec_t* recPtr = CreateRec();

...

if (x > LIMIT)

{

goto fault;

}

...

SaveRec(recPtr);

return SUCCESS;

fault:

ReleaseRec(recPtr);

return FAILED;

}

Global Variables

Global variables are variables that are exported to other modules (i.e., have a scope that spans multiple files).

Global variables are dangerous because:

they don't allow protections from multithreaded race conditions,

they reduce maintainability by increasing coupling.

Globals must not be used. Use accessor functions instead.

Note

file-scope static variables are fine.

Extern

When global variables are not used and all inter-module interfaces are defined in header files, the "extern" keyword is not needed. Don't use it. Use of "extern" is an indication of poor coding practices.

Heap

Depending on the algorithm used, dynamic memory allocation using a memory heap (i.e., using malloc, free, and variants of malloc, such as calloc, realloc, strdup, etc.) can lead to heap fragmentation, resulting in unexpected runtime failures. Furthermore, heap allocation and deallocation can be very slow in some cases.

Use memory pools instead. Memory pools eliminate internal fragmentation, run in O(1) time (for both allocation and deallocation), can be named for diagnostics purposes, allow finer-grained memory allocation statistics collection, and can provide OO constructor and destructor functionality.

Function Parameter Lists

The number of parameters passed to any given function should be kept as low as possible. Functions with less parameters tend to be easier to understand and easier to use. As a general guideline, C functions should have 4 parameters or less.

Const Pointers

Pointer type function parameters must be declared const if the object pointed to will not be modified by the function it is being passed to.

Pointer type return values must be declared const if the object being returned must not be modified by the caller.

Error Handling

Error handling for runtime errors, such as unexpected data received over a network, or timeouts while trying to contact a server, should either be handled within a function, or indicated to the caller by returning an error code. Generally le_result_t is used for this purpose.

It can also be useful to insert checks which should never fail. Even though these checks should never fail, they are useful for: detecting bugs early; and limiting the damage of uncaught bugs. Examples of such checks include:

Checking parameters are within range accepted by an API function.

Checking a pointer is not NULL before dereferencing it if the pointer should never be NULL at that point in the code.

Checking the return value of a function, if the function can never fail as called. E.g. strtol() if the string has already been validated to be a small integer.

Since the developer does not know why such checks have failed, such checks should exit the process by invoking the LE_FATAL or LE_ASSERT family of macros. This aims to minimize any data corruption by restarting the process with a clean memory space. Using the LE_FATAL family of functions is preferred over LE_ASSERT as LE_FATAL allows logging additional information about the error.

Since invoking LE_FATAL or LE_ASSERT will cause the process to exit, these must not be used for checks which are only unlikely to fail. Checks which are unlikely to fail are runtime errors and should be handled as indicated above. Similarly a developer should consider an alternate recovery method if restarting the process is unlikely to clear the problem, such as reading corrupted data from persistant storage.

Note

For security reasons, malformed messages from network services are always considered runtime errors, even if the service is locally developed or otherwise trusted. All network input should be validated. If it fails validation it should raise a runtime error and any invalid data discarded.

Multithreading

Sometimes multithreading can be a powerful tool, allowing functionally related code to be grouped into a single flow of control where it would otherwise be fragmented into small chunks that can run without blocking. However, multithreading can easily become the source of some of the most nasty bugs.

Function-Like Macros

Function-like macros are preprocessor expressions that are used like function calls, ie:

#define CUBE(x) ((x)*(x)*(x))

Function-like macros are often used for efficiency because the macro is expanded in place which avoids the overhead of a function call.

However, function-like macros have many pitfalls, for example:

// This is an unsafe macro because the argument x is evaluated more than once.

#define CUBE(x) (x*x*x)

int main(int argc, char *argv[])

{

int y = 0;

int x = 3;

y = CUBE(x); // Works fine; y = 9.

x = 2;

y = CUBE(++x); // y = 60 because x is incremented 3 times on most compilers.

Avoid defining function-like macros. Static inline functions should be used in place of function-like macros where possible. If a function-like macro must be defined be aware of the following rules and recommendations: PRE31-C, PRE32-C, PRE00-C, PRE01-C, PRE10-C.

Variable Side Effects

Side effects can cause unexpected results when used as parameters to unsafe macros as illustrated above. It may also be difficult to determine if a library function is implemented as a macro, therefore it is best to avoid using side effects on function parameters unless it is clear that they are not implemented as unsafe macros. See PRE31-C for more information.

Side effects should not be used in operands to sizeof. The sizeof operator generally computes its results at compile time and therefore does not generally evaluate its operands. This can lead to unexpected results if side effects are used in the operand.

See EXP44-C for more information. The order of evaluation of expressions with side effects is also unreliable. For example:

// This is undefined behavior.

i = i++ + 3;

// This is well defined behavior.

i++;

i = i + 3;

Generally, side effects can lead to unexpected behaviors and should be avoided.

Procedural Side Effects

A function is considered to exhibit procedural side effects when it modifies state in a non-obvious way. In the following example, the GetUserID function gets the user ID given a user name. The user ID is returned in an out parameter and the functions return value is a status code indicating possible errors. Although, this function modifies the state of its return value and the out parameter, uidPtr, these modifications are not considered procedural side effects because they obvious from the functions declaration. However, the function also sets the shell program that is used when the user logins in, if the shell program is not already set. This is not obvious from the function declaration and is considered a procedural side effect.

Procedural side effects makes program logic more difficult to follow and should be avoided.

Signals

Signals are kernel generated messages that cause asynchronous handlers to be called. Properly using signals is difficult due to the many subtle issues associated with asynchronous handlers. It is recommended that the synchronous le_signals() API be used instead. If asynchronous signal handlers must be used be aware of the following issues:

Only async-safe functions should be called in a signal handler.

Mutexes cannot be used in a signal handler.

Standard signals are queued.

Real time signals are queued.

Signal dispositions are per process.

Signal dispositions are inherited through a fork but not an exec.

Signals are delivered to a process not a thread. If multiple threads have handlers for the same signal there is no guarantee which handler will be called.

Asynchronous signal handling should be implemented with care.

Bit Fields

Bit fields are sometimes used to store flag values, ie:

struct

{

unsignedint northZone : 1;

unsignedint eastZone : 1;

unsignedint westZone : 1;

unsignedint southZone : 1;

}

LightSwitch;

LightSwitch.northZone = 0;

LightSwitch.eastZone = 0;

LightSwitch.westZone = 0;

LightSwitch.southZone = 0;

However, the internal layout of the bit fields in a structure is up to the compiler (compiler decides how to align and pad the bit fields). This can lead to misunderstandings of how a bit field should be accessed. For example, because bit fields are often packed into a single storage unit the following code contains a race condition.

struct

{

unsignedint northZone : 1;

unsignedint eastZone : 1;

unsignedint westZone : 1;

unsignedint southZone : 1;

}

LightSwitch;

staticvoid* Thread1(void* contextPtr)

{

LightSwitch.northZone = 1;

return NULL;

}

staticvoid* Thread2(void* contextPtr)

{

LightSwitch.eastZone = 2;

return NULL;

}

See EXP11-C, CON32-C, INT12-C for other issues related to bit fields. Bit fields are almost always unnecessary and should be avoided.

Flexible Arrays

Flexible arrays are declared by having an array as the last element of a struct, for example:

As can be seen from the code example above memory for the flexible array needs to be allocated dynamically. The programmer should also remember to account for the array size when copying arrays and when passing the struct as a parameter.

staticstruct DynamicArray

{

size_t len;

char data[];

}

staticint Bar(struct DynamicArray someData)

{

// Because the struct is passed by value the struct is copied and again does not account for the