Visual Basic/Event-Driven Design: Difference between revisions
Content deleted Content added
No edit summary |
m Undo revision 352594 by 212.219.117.143 (Talk) : unexplained removal of text |
||
Line 13:
<references/>'''Advantages of event-driven programming:'''
Event-driven programming is often termed as unstructured programming as it can never be said which piece of code will get executed unless we know which event occured. But this very fact contibutes to the major advantage of event-driven programming. With this approach, we can be sure of some components of a program(or software for that matter) running successfully while we work on others.
Another advantage associated with it is the convenience offered to both the end-user and the programmer. Events can be initiated by the user (like clicking a button). So it gives the user a feel of control over the system. On the other hand, programmer can put some very crucial code for very crucial events such as loading of a form, where several initializations and checks can be performed.
[[Category:Computer_programming]]
| |||