青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品

HRESULT -- Structure of COM Error Codes

SCODEs on 16-bit platforms are divided into four fields: a severity code, a context field, a facility field, and an error code. The following illustration shows the format of an SCODE on a 16-bit platform; the numbers indicate bit positions:

image

HRESULTs and SCODEs on 32-bit platforms have the following format:

image

The high-order bit in the HRESULT or SCODE indicates whether the return value represents success or failure. If set to 0, SEVERITY_SUCCESS, the value indicates success. If set to 1, SEVERITY_ERROR, it indicates failure.

The context field is reserved in the SCODE on 16-bit platforms and does not exist in the version for 32-bit platforms. The R, C, N, and r bits are also reserved.

The facility field in both versions indicates the system service responsible for the error. Microsoft allocates new facility codes as they become necessary. Most SCODEs and HRESULTs set the facility field to FACILITY_ITF, indicating an interface method error.

 

vc6中的說明(in winerror.h line:7860)

////////////////////////////////////
//                                //
//     OLE Error Codes            //
//                                //
////////////////////////////////////

//
// OLE error definitions and values
//
// The return value of OLE APIs and methods is an HRESULT.
// This is not a handle to anything, but is merely a 32-bit value
// with several fields encoded in the value.  The parts of an
// HRESULT are shown below.
//
// Many of the macros and functions below were orginally defined to
// operate on SCODEs.  SCODEs are no longer used.  The macros are
// still present for compatibility and easy porting of Win16 code.
// Newly written code should use the HRESULT macros and functions.
//

//
//  HRESULTs are 32 bit values layed out as follows:
//
//   3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
//   1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
//  +-+-+-+-+-+---------------------+-------------------------------+
//  |S|R|C|N|r|    Facility         |               Code            |
//  +-+-+-+-+-+---------------------+-------------------------------+
//
//  where
//
//      S - Severity - indicates success/fail
//
//          0 - Success
//          1 - Fail (COERROR)
//
//      R - reserved portion of the facility code, corresponds to NT's
//              second severity bit.
//
//      C - reserved portion of the facility code, corresponds to NT's
//              C field.
//
//      N - reserved portion of the facility code. Used to indicate a
//              mapped NT status value.
//
//      r - reserved portion of the facility code. Reserved for internal
//              use. Used to indicate HRESULT values that are not status
//              values, but are instead message ids for display strings.
//
//      Facility - is the facility code
//
//      Code - is the facility's status code
//

Common facility fields are described in the following table.

Facility Field Value Description
FACILITY_DISPATCH 2 For late-binding IDispatch interface errors.

FACILITY_ITF

4 For most status codes returned from interface methods. The actual meaning of the error is defined by the interface. That is, two HRESULTs with exactly the same 32-bit value returned from two different interfaces might have different meanings.
FACILITY_NULL 0 For broadly applicable common status codes such as S_OK.
FACILITY_RPC 1 For status codes returned from remote procedure calls.
FACILITY_STORAGE 3

For status codes returned from IStorage or IStream method calls relating to structured storage. Status codes whose code (lower 16 bits) value is in the range of DOS error codes (that is, less than 256) have the same meaning as the corresponding DOS error.

FACILITY_WIN32 7 Used to provide a means of handling error codes from functions in the Win32 API as an HRESULT. Error codes in 16-bit OLE that duplicated Win32 error codes have also been changed to FACILITY_WIN32.
FACILITY_WINDOWS 8 Used for additional error codes from Microsoft-defined interfaces.
VC6中的定義    
FACILITY_SSPI 9  
FACILITY_SETUPAPI 15  
FACILITY_CONTROL 10  
FACILITY_CERT 11  
FACILITY_INTERNET 12  
FACILITY_MEDIASERVER 13  
FACILITY_MSMQ 14  

The code field is a unique number that is assigned to represent the error or warning.

By convention, HRESULTs generally have names in the following format:

        Facility_Severity_Reason

Facility is either the facility name or some other distinguishing identifier; Severity is a single letter, S or E, that indicates whether the function call succeeded (S) or produced an error (E); and Reason is an identifier that describes the meaning of the code. For example, the status code STG_E_FILENOTFOUND indicates a storage-related error has occurred; specifically, a requested file does not exist. Status codes from FACILITY_NULL omit the Facility_ prefix.

Error codes are defined within the context of an interface implementation. Once defined, success codes cannot be changed or new success codes added. However, new failure codes can be written. Microsoft reserves the right to define new failure codes (but not success codes) for the interfaces described in FACILITY_ITF or in new facilities.

posted on 2008-08-11 10:33 FongLuo 閱讀(525) 評論(0)  編輯 收藏 引用

<2008年8月>
272829303112
3456789
10111213141516
17181920212223
24252627282930
31123456

導航

常用鏈接

留言簿

隨筆分類(11)

隨筆檔案(79)

文章檔案(1)

收藏夾(38)

學習網站

一般網站

最新隨筆

搜索

積分與排名

最新評論

閱讀排行榜

青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品
  • <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            欧美在线首页| 亚洲欧洲日韩女同| 亚洲午夜久久久久久久久电影院| 久久久精品午夜少妇| 午夜激情综合网| 亚洲主播在线观看| 香蕉久久一区二区不卡无毒影院| 一二三区精品| 午夜精品久久久久久久男人的天堂 | 国产精品观看| 国产麻豆综合| 国产自产高清不卡| 亚洲日本一区二区三区| 亚洲图片欧美日产| 米奇777在线欧美播放| 欧美国产精品人人做人人爱| 这里只有精品视频| 亚洲午夜精品久久久久久浪潮 | 国产日韩精品久久久| 好吊日精品视频| 99爱精品视频| 欧美高清视频www夜色资源网| 日韩亚洲国产精品| 午夜在线一区二区| 国产精品稀缺呦系列在线| 日韩亚洲视频在线| 亚洲片在线资源| 久久成人精品| 国产一区在线视频| 久久国产欧美| 久久久久久香蕉网| 亚洲国产精品一区制服丝袜| 欧美一区二区三区精品电影| 亚洲欧美激情视频在线观看一区二区三区| 欧美激情第一页xxx| 亚洲美女av电影| 日韩特黄影片| 国产酒店精品激情| 快播亚洲色图| 欧美日本一区二区高清播放视频| 日韩手机在线导航| 亚洲伊人一本大道中文字幕| 国产农村妇女毛片精品久久莱园子 | 在线亚洲欧美专区二区| 国产精品久久久久久模特| 亚洲一区二区精品在线观看| 一本久久综合亚洲鲁鲁五月天| 亚洲国产第一页| 欧美日本一区二区三区 | 国内成+人亚洲+欧美+综合在线| 玖玖玖免费嫩草在线影院一区| 久久免费精品视频| 亚洲影院高清在线| 久久夜色精品一区| 欧美一区二区三区久久精品茉莉花| 欧美一区二区三区四区在线 | 欧美国产日韩一区二区| 亚洲欧美综合精品久久成人| 久久久91精品国产一区二区三区 | 狠狠色伊人亚洲综合网站色| 亚洲第一视频| 黄网动漫久久久| 亚洲永久在线观看| 亚洲尤物影院| 欧美国产精品va在线观看| 麻豆久久婷婷| 精品二区久久| 久久久久久久高潮| 久久国产视频网站| 狠狠v欧美v日韩v亚洲ⅴ| 亚洲性人人天天夜夜摸| 亚洲一级黄色片| 欧美精品免费播放| 亚洲国产成人午夜在线一区| 精品99一区二区三区| 久久久久国产一区二区| 欧美三级电影网| 国产一区导航| 久久精品五月婷婷| 久久免费精品日本久久中文字幕| 国产美女精品在线| 欧美在线免费观看| 久久免费99精品久久久久久| 伊人成综合网伊人222| 久久伊人精品天天| 亚洲毛片视频| 久久精品国产亚洲一区二区| 亚洲夫妻自拍| 欧美精品国产一区二区| 亚洲视频综合| 久久先锋资源| 亚洲一区二区三区久久| 国产一区二区三区久久久| 久久久久国产精品麻豆ai换脸| 亚洲日本精品国产第一区| 性欧美xxxx视频在线观看| 在线播放精品| 国产精品日韩一区| 欧美日韩精品是欧美日韩精品| 欧美在线短视频| 亚洲自拍偷拍麻豆| 欧美激情精品久久久久久大尺度| 亚洲综合色噜噜狠狠| 亚洲精品欧洲精品| 在线日韩电影| 国产日韩欧美综合精品| 国产精品高精视频免费| 欧美金8天国| 免费中文字幕日韩欧美| 久久五月婷婷丁香社区| 久久久久久久网站| 久久久久国产精品一区| 欧美一区在线视频| 欧美一区二区三区在线播放| 午夜精品在线| 亚洲一级一区| 亚洲网址在线| 久久久久久亚洲综合影院红桃 | 欧美尤物巨大精品爽| 亚洲影院一区| 久久精品人人做人人爽| 欧美在线精品免播放器视频| 午夜在线视频一区二区区别| 亚洲免费一级电影| 久久精品91久久香蕉加勒比| 毛片av中文字幕一区二区| 久久久久国产精品一区三寸| 久久综合中文字幕| 国产精品va在线播放| 黄色成人av| 亚洲一区二区在线观看视频| 欧美一级午夜免费电影| 亚洲激情中文1区| 久久成人精品一区二区三区| 欧美日韩在线一区二区| 1769国内精品视频在线播放| 在线视频中文亚洲| 亚洲大片一区二区三区| 亚洲欧美日韩在线播放| 欧美在线关看| 亚洲图片自拍偷拍| 欧美日产一区二区三区在线观看| 国产伦精品一区二区三区照片91 | 亚洲伦理一区| 久久综合久久美利坚合众国| 亚洲精品国产欧美| 你懂的成人av| 日韩午夜在线| 亚洲精品日韩在线观看| 美国十次了思思久久精品导航| 国产欧美精品日韩精品| 欧美日韩一二三区| 一二三四社区欧美黄| 日韩一二在线观看| 欧美连裤袜在线视频| 99国产精品99久久久久久粉嫩| 欧美激情第3页| 欧美激情欧美激情在线五月| 亚洲精品视频啊美女在线直播| 亚洲国产精品成人一区二区| 欧美成人国产一区二区| 中文国产一区| 亚洲欧美日韩精品在线| 国内精品久久久| 91久久精品久久国产性色也91| 一区二区三区精密机械公司| 亚洲视频久久| 一区在线播放视频| 亚洲精品在线一区二区| 国产精品欧美日韩久久| 亚洲高清免费| 一区二区在线视频播放| 亚洲一区二区三区中文字幕| 亚洲成人在线网| 一区二区三区久久精品| 亚洲国产美女精品久久久久∴| 亚洲国产精品高清久久久| 国产精品亚洲一区二区三区在线| 久久理论片午夜琪琪电影网| 国产精品久久久久影院亚瑟| 媚黑女一区二区| 国产日韩亚洲欧美综合| 亚洲一区免费看| 亚洲综合成人在线| 国产精品www994| 亚洲午夜久久久久久久久电影网| 亚洲人在线视频| 久久久久久国产精品mv| 蜜臀久久久99精品久久久久久 | 欧美日韩专区在线| 久久精品99无色码中文字幕| 亚洲日韩欧美视频一区| 亚洲一区观看| 欧美成人精精品一区二区频| 亚洲图片在线| 美女黄毛**国产精品啪啪| 午夜欧美大尺度福利影院在线看| 亚洲国产欧美一区| 国内精品一区二区| 国产精品手机视频|