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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a20c6510248c3334 X-Google-Attributes: gid103376,public From: Ray Blaak Subject: Re: Visual Basic and ADA95 Date: 1999/10/20 Message-ID: #1/1 X-Deja-AN: 538698284 Sender: blaak@vault83.infomatch.bc.ca References: <380CBFA4.BB241336@fmr.com> X-Trace: news.bctel.net 940480112 207.34.170.83 (Wed, 20 Oct 1999 21:28:32 PDT) NNTP-Posting-Date: Wed, 20 Oct 1999 21:28:32 PDT Newsgroups: comp.lang.ada X-Complaints-To: news@bctel.net Date: 1999-10-20T00:00:00+00:00 List-Id: "Vladimir Olensky" writes: > Mike Biedronski wrote in message <380CBFA4.BB241336@fmr.com>... > As for communicating between front end and Ada core > system there are several options: > > 1. [DLL] > 2. [sockets, pipes, CORBA] > 2.1 [java and sockets/JNI] If I had to do it I would use the DLL approach, but an ActiveX (i.e. automation) DLL, rather than a direct DLL. This gives a loose binding similar to CORBA, but is much more natural to use on a Windows platform with VB than any of the other choices mentioned so far (assuming, of course, that you require VB for the front end). The only other missing piece is an ActiveX buillder for Ada to generate automation (COM) interfaces for a DLL. Check out http://www.adapower.com/com for one. There may be others (may the Windows GNAT documentation?). -- Cheers, The Rhythm is around me, The Rhythm has control. Ray Blaak The Rhythm is inside me, blaak@infomatch.com The Rhythm has my soul.