TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type:
text/plain; charset=us-ascii
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Subject:
From:
David Botton <[log in to unmask]>
Date:
Fri, 17 Sep 1999 10:10:23 -0700
MIME-Version:
1.0
X-To:
"Richard L. Conn" <[log in to unmask]>
Reply-To:
Parts/Attachments:
text/plain (50 lines)
I'll try to put together some sample code and
documentation on how to do all three integration
options with VB.

I already described one. The third way is just an
extension of the first.

Method 2:

After creating the Ada DLL using whatever method your
compiler uses, you then hand create VB bindings to the
DLL entries you will be using.

Method 3:

Create the Ada DLL, but then create a Type Library
using the Module class. This will let you create a
binary spec for the Ada DLL that can then be loaded in
to VB or any other language supporting Type Library
binding (BTW Ada now supports this by running BindCOM
- http://www.adapower.com/com -- on the Type Library.
BindCOM is not just for creating COM/ActiveX
bindings.)

Type libraries also let you define constants,
enumerations, record types, C style unions, and more,
for use with your DLL.

VB loads the Type Library and takes care of all the
types and bindings for you.

David Botton


--- "Richard L. Conn" <[log in to unmask]> wrote:
> That's very good, David,
>
> I like your extended examples with COM and DLL.
>
> We should build our combined works together into an
> integrated picture.
> I think it's a good story to tell, along with the
> web interface story.
>
> Rick

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

ATOM RSS1 RSS2