IDEAS home Printed from https://ideas.repec.org/a/aes/infoec/vxiiy2008i1p124-130.html
   My bibliography  Save this article

From Errors Treatment to Exceptions Treatment Regarding the Execution Control over Visual Basic Programs

Author

Listed:
  • Cristina Raluca POPESCU
  • Gheorghe POPESCU
  • Veronica Adriana POPESCU

Abstract

In order to comply with the quality standards and with the best practices, the execution of the professional programs must be rigorously controlled so that to avoid occurrence of unpredictable situations that might generate anomalies and could lead to computer blockage, forced termination of the execution and data loss. In traditional programming languages, including Visual Basic 6, the concept of error is extremely evolved. It is considered as error any situation in which the program fails to execute correctly, regardless if such anomaly is generated by a software or hardware cause. Nowadays the modern platforms, including VB.NET have introduced a new concept: exception. Unfortunately, perhaps by mistake, exception is assimilated by many IT specialists as an exceptional (extraordinary) situation or a rare situation.We agree with the opinion of those IT specialists asserting that error is strictly dependant on the programmer, when he/she fails in correctly generating the application’s structures, whilst exception is a situation not fitting in the usual natural execution or as desired by the programmer or user, without meaning that it occurs more often or more rarely.Designing robust programs implies for such not to terminate abnormally or block, not even upon receiving improper parameters. Two aspects are referred to: the behavior regarding low level errors (caused by the operation system, memory allocation, reading/writing in files or hardware malfunctions) and the reaction to the user’s errors, such as providing incorrect input data or incorrect use of operations in respect with their sequences. Notwithstanding what platform is used in designing the programs and regardless the controversy between the specialists, in order for the execution to be terminated under the program’s control, the commands that might generate anomalies and interruptions should be strictly monitored. Implicitly, the execution control should be handed over to specialized procedures, able to analyze the causes generating the anomaly and to launch into execution the most adequate remedy processes, or, as a last resort, to allow for the controlled termination of the program. These elements that are specific to Visual Basic programming are unitarily and systematically presented both by the traditional unstructured approach of errors and by the modern vision of structured exceptions’ approach, finally emphasizing the uncontestable advantages of the .NET platform.

Suggested Citation

  • Cristina Raluca POPESCU & Gheorghe POPESCU & Veronica Adriana POPESCU, 2008. "From Errors Treatment to Exceptions Treatment Regarding the Execution Control over Visual Basic Programs," Informatica Economica, Academy of Economic Studies - Bucharest, Romania, vol. 0(1), pages 124-130.
  • Handle: RePEc:aes:infoec:v:xii:y:2008:i:1:p:124-130
    as

    Download full text from publisher

    File URL: http://revistaie.ase.ro/content/45/19%20-%20popescu_gheorghe.pdf
    Download Restriction: no
    ---><---

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:aes:infoec:v:xii:y:2008:i:1:p:124-130. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Paul Pocatilu (email available below). General contact details of provider: https://edirc.repec.org/data/aseeero.html .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.