From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID,
	RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,f348a8d7ddab6952,start
X-Google-Attributes: gid103376,public
From: "Paul Whittington" <paul@sage.inel.gov>
Subject: Bug reports for Win32Ada Binding
Date: 1996/08/27
Message-ID: <01bb9466$01037740$24af1486@pc-phw.inel.gov>#1/1
X-Deja-AN: 176858518
organization: INEL
newsgroups: comp.lang.ada
Date: 1996-08-27T00:00:00+00:00
List-Id: <comp.lang.ada>


Is there an organization somewhere that's maintaining the Win32Ada binding
specification?

Where does one report bugs/potential bugs?

Here's my problem:

     In the Win32.WinError package there's a definition for HRESULT => type
HRESULT is new LONG;
     In the Win32.ObjBase package there's a definition for HRESULT => type
HRESULT is new Win32.LONG;

GREPing the C headers I get:

     grep "typedef *LONG *HRESULT" * 

     WTYPES.H:typedef LONG HRESULT;  
     WTYPES.IDL:typedef LONG HRESULT;

So it seems that in C there's only one definition for what an HRESULT is,
but in Win32Ada there's two.  This makes using HRESULTs a little clumsy in
that one must use Unchecked_Conversion.

TTFN Paul