Execution (computing): Difference between revisions

Content deleted Content added
m Reverted edits by 2601:603:5280:2E30:50CE:6CA1:9725:9660 (talk) to last version by MCE89
Tags: Rollback Mobile edit Mobile web edit Advanced mobile edit
Tag: Reverted
Line 37:
When a program is to be executed, a [[loader (computing)|loader]] first performs the necessary [[memory (computers)|memory]] setup and links the program with any [[dynamic linking|dynamically linked]] [[software library|libraries]] it needs, and then the execution begins starting from the program's [[entry point]]. In some cases, a language or implementation will have these tasks done by the language runtime instead, though this is unusual in mainstream languages on common consumer operating systems.
 
Some program debugging can only be performed (or is more efficient or accurate when performed) at runtime. [[Logic error]]s and [[array data structure|array]] bounds checking are examples. For this reason, some programming [[software bug|bugs]] are not discovered until the program is tested in a [[production environment]] with real data, despite sophisticated compile-time checking and pre-release testing. In this case, the end-user may encounter a "runtime error" message.
 
=== Application errors (exceptions) ===