🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: borland.public.cppbuilder.nativeapi
5 messages
5 total messages Started by Malcolm Smith Mon, 12 May 2008 10:51
HRESULT structure
#357
Author: Malcolm Smith
Date: Mon, 12 May 2008 10:51
16 lines
1307 bytes
Does anyone know which of these two Microsoft links contains the correct 
information:

http://msdn.microsoft.com/en-us/library/cc231198.aspx

http://msdn.microsoft.com/en-us/library/ms690088(VS.85).aspx

They both describe the structure of a HRESULT, but they are different.

I only need to know as I am about to refer to this structure in a document 
(for informational reasons) and don't want to provide the wrong information.

TIA.

-- 
Malcolm Smith
Re: HRESULT structure
#358
Author: Alan Bellingham
Date: Mon, 12 May 2008 11:15
27 lines
1864 bytes
"Malcolm Smith" <nospam@nospam.com> wrote:

>Does anyone know which of these two Microsoft links contains the correct 
>information:
>
>http://msdn.microsoft.com/en-us/library/cc231198.aspx
>
>http://msdn.microsoft.com/en-us/library/ms690088(VS.85).aspx
>
>They both describe the structure of a HRESULT, but they are different.
>
>I only need to know as I am about to refer to this structure in a document 
>(for informational reasons) and don't want to provide the wrong information.

The latter link would appear to be talking about HRESULTs on a 16-bit
platform and is therefore probably not terribly relevant these days.

The former is definitely more comprehensive, though it doesn't contain
the information I was looking for some 15 minutes ago.

(I was trying to find out the name for 0x800706BA. Turns out it was
RPC_S_SERVER_UNAVAILABLE, or at least, the low 16 bits were.)

Alan Bellingham
-- 
Team Browns
ACCU Conference 2009: to be announced
Re: HRESULT structure
#359
Author: Alan Bellingham
Date: Mon, 12 May 2008 11:27
15 lines
1523 bytes
Alan Bellingham <alan@lspace.org> wrote:

>The latter link would appear to be talking about HRESULTs on a 16-bit
>platform and is therefore probably not terribly relevant these days.

Ah, hold on, the lower diagram is talking about the 32-bit version.

The S and R single bit fields in that diagram are the two bit Sev field
in the first link. But anyway, I'd go with your first link - it appears
to be much less confusing.

Alan Bellingham
-- 
Team Browns
ACCU Conference 2009: to be announced
Re: HRESULT structure
#360
Author: Malcolm Smith
Date: Mon, 12 May 2008 12:51
25 lines
1947 bytes
What's confusing, though, is that one diagram has 4 bits (Sev + C + R), 
whereas the other has 5 bits ( S + R + C + N + r) before the Facility bits 
are encountered (reading left to right).

-- 
Malcolm Smith


"Alan Bellingham" <alan@lspace.org> wrote in message 
news:m5ag24ddilh2eb53ccnucth2l6b8t7lmsg@4ax.com...
> Alan Bellingham <alan@lspace.org> wrote:
>
>>The latter link would appear to be talking about HRESULTs on a 16-bit
>>platform and is therefore probably not terribly relevant these days.
>
> Ah, hold on, the lower diagram is talking about the 32-bit version.
>
> The S and R single bit fields in that diagram are the two bit Sev field
> in the first link. But anyway, I'd go with your first link - it appears
> to be much less confusing.
>
> Alan Bellingham
> -- 
> Team Browns
> ACCU Conference 2009: to be announced 
Re: HRESULT structure
#361
Author: Bob Gonder
Date: Mon, 12 May 2008 14:52
11 lines
1412 bytes
Alan Bellingham wrote:

>The S and R single bit fields in that diagram are the two bit Sev field
>in the first link. But anyway, I'd go with your first link - it appears
>to be much less confusing.

The first (older?) page certainly has more information,
and would be good to document.
The second page (vs.85, newer?) likely has corrected current format.

I also think the second looks better with single bit S being success/fail.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads