Handling Errors and Exceptions
http://delphi.about.com/od/objectpascalide/a/errorexception.htm
Unfortunately, building applications includes coding.
Regardless of how carefully you write/debug your program,
it will be impossible to imagine every situation that can go wrong.
Inexperienced user might, for example,
try to open a nonexisting file or input a bad value into a data field.
Users make mistakes and we should be prepared to handle/prevent these errors
wherever and whenever possible.
Errors, Exceptions?
An exception is generally an error condition or other event
that interrupts normal flow of execution in an application.
Whenever an error results from processing a line of code,
Delphi creates (raises) an object descendent from TObject called the exception object.
Guarded Blocks
An application responds to an exception either by executing some termination code,
handling the exception, or both.
The way to enable error/exception trapping within a given code,
the exception must occur within a guarded block of statements.
The general code looks like:
try
{guarded block of code}
except
on <ESomeException> do
begin
{exception block-handles SomeException}
end;
end;
A try / except statement executes the statements in the guarded block of code.
If the statements execute without any exceptions being raised,
the exception block is ignored, and control is passed to the statement following the end keyword.
Example:
Zero:=;
try
dummy:= / Zero;
except
on EZeroDivide do
MessageDlg('Can not divide by zero!', mtError, [mbOK], ) ;
end;
Protecting Resources
When a section of code acquires a resource, it is often necessary to ensure that the resource is released again
(or you might get a memory leak ), regardless of whether the code completes normally or is interrupted by an exception.
In this case, the syntax usesfinally keyword and looks like:
{some code to allocate resources}
try
{guarded block of code}
finally
{termination blok - code to free resources}
end; { Example } AboutBox:=TAboutBox.Create(nil) ;
try
AboutBox.ShowModal;
finally
AboutBox.Free;
end;
Application.OnException
If your application doesn't handle the error that caused the exception,
then Delphi will use its default exception handler - it will just pop up a message box.
You may consider writing code in the OnException event for TApplication object,
in order to trap errors at the application level.
Break On Exceptions
When building a program with exception handling,
you may not want Delphi to break on Exceptions.
This is a great feature if you want Delphi to show where an exception has occurred;
however, it can be annoying when you test your own exception handling.
On Handling Exceptions in Delphi Exception Handling
No code is error free!
Some code is full of "errors" on purpose :)
What's an error in an application? An error, from my general point of view,
is, for example, the wrongly coded solution to a problem.
Such are logic errors that could lead to wrong function results
where everything seems nicely but the result of the application is completely unusable (i.e. wrong).
With logic errors, application might or might not stop working.
An exception is an exceptional condition.
Exceptions include errors in your code where you try to divide numbers with zero,
or you try using freed memory blocks or you try providing wrong parameters to a function.
An exception in an application is not always an error -
if by error we think on those nasty problems with the program where it stop responding.
Exceptions And The Exception Class
As stated, exception are special conditions that require special handling.
When an error-type condition occurs the program raises an exception.
As suggested by Nick Hodges in Exception Handling for Fun and Profit article,
application writers should trap exceptions, exceptions get raised by components and library code on purpose.
You (as the application writer) handle exceptions, to make your application more error-prone,
to respond to the exceptional condition.
In most cases you will find yourself being the application writer and also the library writer.
So you would need to know how to raise exceptions (from your library) and how to handle them (from your application).
I'm sure we all have dozens of units defining some special-to-me classes, interfaces and alike.
For example, I have a class dealing with PDF documents I'm using in several of my applications.
When I code / edit the class I am the library writer, when I'm using the library I'm the application writer.
Let's take a look at handling exceptions...
The article Handling Errors and Exceptions provides some basic guidelines on
how to guard against errors using try/except/end and try/finally/end protected blocks to respond to or handle exceptional conditions.
A simple try/except guarding blocks looks like:
try
ThisFunctionMightRaiseAnException();
except
{ handle any exceptions raised in ThisFunctionMightRaiseAnException() here }
end;
The ThisFunctionMightRaiseAnException might have, in its implementation, a line of code like
raise Exception.Create('special condition!');
he Exception is a special class (one of a few without a T in front of the name) defined in sysutils.pas unit.
The SysUtils unit defines several special purpose Exception descendants
(and thus creates a hierarchy of exception classes )
like ERangeError, EDivByZero, EIntOverflow, etc.
In most cases the exceptions that you would handle in the protected try/except block
would not be of the Exception (base) class but of some special Exception descendant class defined i
n either the VCL or in the library (you or some other developer coded) you are using.
Handling Exceptions Using Try/Except
To catch and handle an exception type you would construct a "on type_of_exception do" exception handler.
The "on exception do" looks pretty much like the classic case statement :
try
ThisFunctionMightRaiseAnException;
except
on EZeroDivide do
begin
{ something when dividing by zero }
end;
on EIntOverflow do
begin
{ something when too large integer calculation }
end;
else
begin
{ something when other exception types are raised }
end;
end;
Note that the else part would grab all (other) exceptions,
including those you know nothing about.
In general, your code should handle only exceptions you actually know how to handle and expect to be thrown.
Also, you should never "eat" an exception:
try
ThisFunctionMightRaiseAnException;
except
end;
Eating the exception means you do not know how to handle the exception
or you do not want users to see the exception or anything in between.
When you handle the exception and you need more data from it
(after all it is an instance of a class) rather only the type of the exception you can do:
try
ThisFunctionMightRaiseAnException;
except
on E : Exception do
begin
ShowMessage(E.Message);
end;
end;
The "E" in "E:Exception" is a temporary exception variable of type specified
after the column character (in the above example the base Exception class).
Using E you can read (or write) values to the exception object, like get or set the Message property.
Who Frees The Exception?
Noticed how exceptions are actually instances of a class descending from Exception?
The raise keyword throws an exception class instance.
You know that what you create (the exception instance is an object) you also need to free .
If, you as a library writer, create an instance, will the application user free it?
Or, who will?
Delphi magic:
handling an exception automatically destroys the exception object.
This means that when you write the code in the "except / end" block - this block (hm, bad wording)
will release the exception memory.
So what happens if ThisFunctionMightRaiseAnException
actually raises an exception and you are not handling it
(this is not the same as "eating" it)?
How Come My App Does Not Crash When number/0 Is Not Handled?
When an unhandled exception is thrown in your code,
Delphi "magically" handles your exception by displaying the error dialog to the user.
In most cases this dialog will not provide enough data for the user (and finally you)
to understand the cause of the exception.
This is controlled by Delphi's top level message loop
where ALL exceptions are being processed
by the global Application object and its HandleException method.
To handle exceptions globally, and show your own more-user-friendly dialog,
you can write code for the TApplicationEvents.OnException event handler.
Note that the global Application object is defined in the Forms unit.
The TApplicationEvents is a component you can use to intercept the events of the global Application object.
Ok, that's it for now.
Next time I'll go into reraising exception.
Handling Errors and Exceptions的更多相关文章
- Python Tutorial 学习(八)--Errors and Exceptions
Python Tutorial 学习(八)--Errors and Exceptions恢复 Errors and Exceptions 错误与异常 此前,我们还没有开始着眼于错误信息.不过如果你是一 ...
- 《The Python Tutorial》——Errors and Exceptions 阅读笔记
Errors and Exceptions 官方文档:https://docs.python.org/3.5/tutorial/errors.html python中所有的异常都继承自BaseExce ...
- [译]The Python Tutorial#8. Errors and Exceptions
[译]The Python Tutorial#Errors and Exceptions 到现在为止都没有过多介绍错误信息,但是已经在一些示例中使用过错误信息.Python至少有两种类型的错误:语法错 ...
- Laravel API Errors and Exceptions: How to Return Responses
Laravel API Errors and Exceptions: How to Return Responses February 13, 2019 API-based projects are ...
- 笔记-python-tutorial-8.errors and exceptions
笔记-python-tutorial-8.errors and exceptions 1. errors and exceptions 1.1. syntax errors >& ...
- STL之Errors and Exceptions
Error Handling STL设计的目标是性能最优化,而不是最安全. 错误检查是极其浪费时间的,因此,STL对于错误处理几乎没有做处理,因此,这对STL的使用者的要求就非常高. 为什么不采取错误 ...
- python异常和错误(syntax errors 和 exceptions)
语法错误 语法错误又被称解析错误 >>> for i in range(1..10):print(i) File "<stdin>", line 1 ...
- Python Errors and Exceptions
1. python中的try{}catch{} 2. raise exception 3. try...except ... else.. 4. finally块 python中的异常处理的keywo ...
- Understanding Asynchronous IO With Python 3.4's Asyncio And Node.js
[转自]http://sahandsaba.com/understanding-asyncio-node-js-python-3-4.html Introduction I spent this su ...
随机推荐
- 45.Jump Game II---贪心---2018大疆笔试题
题目链接 题目大意:与55题类似,只是这里要求出跳数. 法一(借鉴):贪心.cur表示当前能到达的最远距离,pre表示上一次能到达的最远距离,每到一个位置更新一次最远距离cur,如果当前位置超过了上一 ...
- Ubuntu每次开机后提示:检测到系统程序出现问题的解决方法
首先,错误报告存放位置: cd /var/crash/ ls //可以查看错误报告 1 2 sudo rm /var/crash/* //删除该目录下的所有文件 1 但是,这只是删除掉的是错误报告,如 ...
- win10产品密钥 win10专业版激活码key
转载地址:http://www.xitongcheng.com/jiaocheng/xtazjc_article_35407.html https://blog.csdn.net/WangJianku ...
- MyBatis3-与Spring MVC 4集成
继前一篇的例子http://www.cnblogs.com/EasonJim/p/7052388.html,已经集成了Spring框架,现在将改造成Spring MVC的项目,并实现如下功能: 1.不 ...
- 【58沈剑架构系列】DB主从一致性架构优化4种方法
需求缘起 大部分互联网的业务都是“读多写少”的场景,数据库层面,读性能往往成为瓶颈.如下图:业界通常采用“一主多从,读写分离,冗余多个读库”的数据库架构来提升数据库的读性能. 这种架构的一个潜在缺点是 ...
- scrapy 学习笔记1
最近一段时间开始研究爬虫,后续陆续更新学习笔记 爬虫,说白了就是获取一个网页的html页面,然后从里面获取你想要的东西,复杂一点的还有: 反爬技术(人家网页不让你爬,爬虫对服务器负载很大) 爬虫框架( ...
- Cookie机制和Session机制
1. cookie 1. Cookie 是在HTTP协议下,服务器或脚本可以维护客户工作站上信息的一种方式.Cookie 是由 Web服务器保存在用户浏览器(客户端)上的小文本文件(内容通常经过加密) ...
- oracle去掉字段值中的某些字符串
我想去掉字段值中的“_” select replace(fdisplayname,'_','') from SHENZHENJM1222.B replace 第一个参数:字段/值,第二个参数时替换字符 ...
- bzoj 1132 几何
思路:我刚开始算三角形的方法是原点叉积三条边,然后计算每条边向量积的贡献,但是对于同一条线上的点 有时候没有办法抵消掉..... 看网上的思路是对于一个三角形的面积通过两条边的叉积获得,然后枚举一个点 ...
- 去除win7桌面图标小箭头.bat
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Icons" ...