Error Handling
At the source code level, all error values consist of three parts, separated
by underscores. The first part is the prefix that identifies the facility
associated with the error, the second part is E for error, and the third part is a
string that describes the actual condition. For example, STG_E_MEDIUMFULL is
returned when there is no space left on a hard disk. The STG prefix indicates the
storage facility, the E indicates that the status code represents an error, and
the MEDIUMFULL provides specific information about the error. Many of the
values that you might want to return from an interface method or function are
defined in winerror.h.
Success, warning, and error values are returned using a 32-bit number known as
a result handle, or HRESULT
. HRESULTs are really not handles to anything, but merely 32-bit values with
several fields encoded in the value. A zero result indicates success and a
non-zero result indicates failure.
HRESULTs work differently depending on the platform you are using. On 16-bit
platforms, an HRESULT is generated from a 32-bit value known as a status code,
or SCODE. On 32-bit platforms, an HRESULT is the same as an SCODE; they are
synonymous. In fact, the SCODE is no longer used. 32-bit OLE uses only HRESULTs.
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database