Re: HRESULT
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:qv1tu3tft96q1ule4vck2olnmvl638kh6n@4ax.com...
Yes, those values are not HRESULT values and cannot be used as such. This
is news?
What is bogus is some values in winerror.h are HRESULTs and not others.
Furthermore, the ones that are not can still be used in functions that take
HRESULTs such as FormatMessage().
It is not news this is screwed up. What made you think I was talking about
something new?
Well, that's the confusion. What sane system would require the caller
(me)
to know whether I have to call HRESULT_FROM_WIN32() to get an 'HRESULT'
that I can pass to the SUCCEEDED() macro, or whether I can use what is
returned from GetLastError() directly? Pure nonsense.
****
You shouldn't have to know. The documentation will tell you what kinds of
errors are
returned.
Oh please. We're talking about an error numbering system. If the best they
can do is come up with an obscure system that makes the user responsible for
things that should be automatic (like all the error values listed in a
header should be treated similarly) then the implementation is insane.
I think we can rightly argue that the documentation does NOT tell us this
is
what is insane...
The fact that some things are not not documented is bad. The fact that some
are documented does not justify the fact that they need to be documented
when the system should be more intuitive.
Anyway, I started this sub-thread because I thought I did not understand
HRESULT's, but I see that for the most part they are just as screwed up as I
had previously thought. Thanks to Check Abdoul for the info about the
HRESULT_FROM_WIN32 macro. That's the only signal in the rest of this noise.
-- David