Difference between revisions of "Event-driven programming"
Karl Jones (Talk | contribs) (→External links) |
Karl Jones (Talk | contribs) (→See also) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 15: | Line 15: | ||
* [[Closure (computer programming)]] | * [[Closure (computer programming)]] | ||
* [[Computer programming]] | * [[Computer programming]] | ||
| + | * [[Event handling]] | ||
* [[Programming paradigm]] | * [[Programming paradigm]] | ||
| Line 23: | Line 24: | ||
[[Category:Computer programming]] | [[Category:Computer programming]] | ||
[[Category:Software]] | [[Category:Software]] | ||
| − | [[Category: | + | [[Category:Software development]] |
Latest revision as of 07:55, 8 May 2016
In computer programming, event-driven programming is a programming paradigm in which the flow of the program is determined by events such as user actions (mouse clicks, key presses), sensor outputs, or messages from other programs/threads.
Description
Event-driven programming is the dominant paradigm used in graphical user interfaces and other applications (e.g. JavaScript web applications) that are centered on performing certain actions in response to user input.
In an event-driven application, there is generally a main loop that listens for events, and then triggers a callback function when one of those events is detected.
In embedded systems the same may be achieved using hardware interrupts instead of a constantly running main loop.
Event-driven programs can be written in any programming language, although the task is easier in languages that provide high-level abstractions, such as closures.
See also
External links
- Event-driven programming @ Wikipedia
