C

C is dangerous stuff...

K&R C

C89

C99

C11

ANSI C

These versions all have minor differences altough the later versions tend to maintain backward compatibility

Types are static, although automatic casting can occur under some circumstances

Types have a particular size and layout in memory that can vary across platforms and implementations

Built-in types

Defines the organization and access to memory, by specifying types and names

Defines the way memory is mapped directly

int a[3];

int a[] = {1,2,3};

int *a;

Custom types

typedef unsigned int uint_32;

the memory location is stored in the variable

the contents of the memory location can be obtained through "dereference"

Using * or []

pointer arithmetic

Can be a source of many errors, as you might write to a section of memory that is not intended, causing a crash, or worse...

Or you might try to read from memory which has not been allocated or already freed.

You can get the address of a variable using the & operator

int func(int arg1, ...)

Can be declared before actually being implemented.

Functions can be passed as pointers

for ()

while ()

do {} while()

Scope specific variables which are allocated and freed automatically

Faster than the heap and real-time safe

Smaller

manual allocation and freeing

generally using pointers

Can be a source of memory leaks

Generally needed when data must be shared among functions or libraries or when data must be kept after the function where it is created has finished

Project files

Build systems

gcc

LLVM

Microsoft compiler

Try to avoid compiler warnings!

Step debugging

Memory management and threading bugs

Using a unit testing framework recommended

Test driven development generally a good idea

e.g. ctest