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

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年9月>
31123456
78910111213
14151617181920
21222324252627
2829301234
567891011

導航

常用鏈接

留言簿

隨筆分類(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>
            久久综合99re88久久爱| 亚洲毛片在线看| 欧美亚洲综合久久| 亚洲高清av| 久久xxxx精品视频| 99精品视频免费观看视频| 国产视频亚洲精品| 国产精品成人国产乱一区| 亚洲精品一二| 亚洲欧洲在线一区| 欧美激情精品久久久久久蜜臀 | 久久精品人人做人人爽| 亚洲精品日韩综合观看成人91| 国产欧美一区二区精品性色| 国产精品红桃| 国产精品久久久999| 欧美日韩国产天堂| 欧美色123| 欧美激情视频一区二区三区在线播放 | 亚洲激情视频在线| 亚洲国产日韩在线| 91久久国产综合久久蜜月精品| 在线看欧美视频| 亚洲国产视频a| 日韩午夜在线电影| 亚洲午夜精品久久| 欧美在线一二三区| 制服诱惑一区二区| 亚洲欧美www| 欧美一级理论片| 久久se精品一区精品二区| 久久久成人网| 欧美大片18| 欧美不卡视频一区| 欧美激情第五页| 9l视频自拍蝌蚪9l视频成人| 亚洲一二三四久久| 久久精品综合网| 欧美黄色一区| 国产欧美在线观看| 亚洲国产一区二区视频| 亚洲午夜视频| 亚洲免费在线电影| 欧美成年人网站| 日韩亚洲欧美一区| 久久精品视频免费播放| 欧美美女bb生活片| 国产尤物精品| 亚洲色诱最新| 女女同性女同一区二区三区91| 亚洲人体1000| 久久精品视频在线观看| 欧美日韩在线视频一区二区| 狠狠色2019综合网| 亚洲手机成人高清视频| 麻豆久久婷婷| 亚洲欧美日韩在线高清直播| 亚洲欧美日韩精品久久亚洲区 | 亚洲国产日韩欧美在线图片| 亚洲免费视频在线观看| 老司机精品久久| 国产亚洲欧美另类中文| 亚洲一级二级| 欧美精品一线| 在线视频成人| 亚洲国产成人porn| 欧美日本精品| 艳女tv在线观看国产一区| 亚洲高清不卡一区| 欧美日韩国产bt| 亚洲色图综合久久| 亚洲一区二区动漫| 国产日韩精品视频一区二区三区| 欧美亚洲视频一区二区| 午夜精品久久久久久99热软件| 国产欧美一级| 欧美成人精品在线| 欧美日韩国产一级| 欧美一区激情视频在线观看| 欧美在线视频免费播放| 91久久午夜| 中文在线资源观看视频网站免费不卡| 久久午夜精品一区二区| 日韩一级在线观看| 国产精品综合av一区二区国产馆| 久久精品夜夜夜夜久久| 麻豆av一区二区三区| 亚洲小说春色综合另类电影| 午夜亚洲性色视频| 亚洲人成在线观看网站高清| 99精品视频免费| 狠狠噜噜久久| 一区二区三区色| 亚洲第一主播视频| 亚洲图中文字幕| 亚洲欧洲日夜超级视频| 亚洲一区二区三区四区中文| 亚洲国产黄色片| 午夜精品一区二区在线观看| 亚洲国产片色| 午夜在线电影亚洲一区| 99热这里只有精品8| 欧美一级黄色录像| 一本一本大道香蕉久在线精品| 欧美一二区视频| 亚洲欧美日本伦理| 欧美精品在线观看播放| 玖玖综合伊人| 国产伦精品一区二区三区高清| 最新成人av在线| 在线免费观看日韩欧美| 亚洲欧美日韩电影| 亚洲一区视频在线观看视频| 欧美成人亚洲| 可以看av的网站久久看| 国产精品亚洲人在线观看| 亚洲日本激情| 亚洲欧洲久久| 久久综合伊人77777麻豆| 久久久久久久久一区二区| 国产精品久久久| 野花国产精品入口| 妖精视频成人观看www| 欧美chengren| 亚洲福利电影| 亚洲日本成人网| 欧美不卡一区| 亚洲成人资源| 亚洲精品欧美专区| 欧美国产丝袜视频| 亚洲日韩第九十九页| 日韩视频在线你懂得| 欧美不卡激情三级在线观看| 欧美激情国产高清| 日韩视频永久免费| 欧美久久久久久蜜桃| 亚洲精品在线观看视频| 夜夜嗨av一区二区三区四区| 欧美黑人在线播放| 亚洲精品在线二区| 亚洲小少妇裸体bbw| 国产精品久久久久一区二区三区| 99精品欧美| 欧美在线3区| 在线观看91精品国产入口| 久久人人精品| 91久久综合| 欧美一区二区精品久久911| 国产精品自拍视频| 久久久999国产| 韩日精品视频| 正在播放亚洲| 久久久久久色| 玉米视频成人免费看| 麻豆久久婷婷| 99精品视频免费全部在线| 亚洲欧美一区二区视频| 国产欧美日韩综合| 久久精品国产精品亚洲精品| 欧美高清视频在线播放| 99国产精品自拍| 国产午夜久久| 欧美成人在线影院| 亚洲视频网在线直播| 久久久在线视频| 99视频在线观看一区三区| 国产精品一区二区三区久久久 | 国产精品jizz在线观看美国| 亚洲一区二区三区在线播放| 久久香蕉国产线看观看av| 亚洲精品色婷婷福利天堂| 欧美色播在线播放| 久久av免费一区| 日韩视频在线免费观看| 久久久亚洲精品一区二区三区| 亚洲精品一品区二品区三品区| 国产精品二区影院| 噜噜噜在线观看免费视频日韩 | 欧美高清不卡| 亚洲欧美国产高清| 亚洲承认在线| 国产精品一区二区在线| 欧美国产日产韩国视频| 欧美中文在线免费| 亚洲一区二区三区四区中文| 亚洲国产精品视频| 久久综合色天天久久综合图片| 亚洲视频在线一区| 亚洲毛片在线观看| 亚洲国产第一页| 韩国欧美一区| 国产精品免费视频xxxx| 欧美精品一区三区| 欧美96在线丨欧| 久久久在线视频| 午夜在线a亚洲v天堂网2018| 亚洲视屏一区| 亚洲视频在线观看一区| avtt综合网| 亚洲美女在线观看|