System Programming - Overview

Overview

In system programming more specifically:

• the programmer will make assumptions about the hardware and other properties of the system that the program runs on, and will often exploit those properties (for example by using an algorithm that is known to be efficient when used with specific hardware)
• usually a low-level programming language or programming language dialect is used that:
  • can operate in resource-constrained environments
  • is very efficient and has little runtime overhead
  • has a small runtime library, or none at all
  • allows for direct and "raw" control over memory access and control flow
  • lets the programmer write parts of the program directly in assembly language
• debugging can be difficult if it is not possible to run the program in a debugger due to resource constraints. Running the program in a simulated environment can be used to reduce this problem.

Systems programming is sufficiently different from application programming that programmers tend to specialize in one or the other.

In system programming, often limited programming facilities are available. The use of automatic garbage collection is not common and debugging is sometimes hard to do. The runtime library, if available at all, is usually far less powerful, and does less error checking. Because of those limitations, monitoring and logging are often used; operating systems may have extremely elaborate logging subsystems.

Implementing certain parts in operating system and networking requires systems programming (for example implementing Paging (Virtual Memory) or a device driver for an operating system).