Content deleted Content added
Waynesalhany (talk | contribs) |
No edit summary |
||
Line 2:
Modern languages such as Visual Basic or Java are called non-procedural or event-driven, languages because instead of writing a series of sequential instructions, a programmer defines the actions that the program must perform when certain events occur.
==Notes and references==▼
{{reflist}}▼
[[Category:Query languages]]▼
{{Compu-lang-stub}}▼
The artificial intelligence languages, so called in the old days, such as LISP and PROLOG, are also considered to be non-procedural although the case for LISP a bit murky since the pure LISP is supposed to be a functional language.
Line 16 ⟶ 9:
Also, it is wrong to equate non-procedural with event-driven. Event-driven languages interact with underlying operating system support to respond efficiently to user generated events. The event-response model is extended to also respond to system generated events, such as an attempt to divide by zero, and custom user coded events. Custom events often extend the error handling features of a programming environment. The event handling code is almost always procedural. This is true for Java, C++, C#, Visual Basic and other event-driven languages. I don't know much about LISP and PROLOG so I can't talk about those languages.
▲==Notes and references==
▲{{reflist}}
▲[[Category:Query languages]]
▲{{Compu-lang-stub}}
| |||