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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b7e4340100880cc9 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-15 06:58:20 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!193.251.151.101!opentransit.net!jussieu.fr!enst!enst.fr!not-for-mail From: "David Botton" Newsgroups: comp.lang.ada Subject: Re: gnat ada DLL and VB Date: Wed, 15 Aug 2001 09:53:45 -0400 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: References: <9Src7.1578$bl.79685@news.siol.net> <7i_d7.276991$qc.33250428@news1.rdc1.va.home.com> Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 997883899 39825 137.194.161.2 (15 Aug 2001 13:58:19 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Wed, 15 Aug 2001 13:58:19 +0000 (UTC) To: Return-Path: X-pair-Authenticated: 65.185.64.49 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.4 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: comp.lang.ada mail<->news gateway List-Unsubscribe: , List-Archive: Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: archiver1.google.com comp.lang.ada:11951 Date: 2001-08-15T09:53:45-04:00 The best way to create portable libraries in general is to abstract the OS interface to the Ada code. When you are writing a COM object you don't have to use ADO or any COM objects with in your Ada code. BTW, there is no seperate layer in COM itself when used inproc (DLL base COM object). As for layers in ADO (since you mentioned it), it depends on how you connect. ADO can do ADO/OLEDB -> ODBC -> Server so you get an extra layer of ADO on top of ODBC or you can go direct using ADO/OLEDB drivers to the server skipping ODBC in the middle. In high volume datbase access on WinXX machines ODBC is a very poor option and has problems with multi tasking with most ODBC drivers. ADO (when going direct with OLEDB drivers) does not suffer this and has better performance then ODBC in general. I know that some may disagree with me, but not using native toolkits (when they are the best tool for the job) on platforms is a sign of lazy programming and poor design. On Windows 9X/NT/2K/XP/CE, the shared library of choice is COM and the data access method is ADO/OLEDB. DLLs are second class citizens on Windows today. Sort of like .com instead of .exe :-) David Botton ----- Original Message ----- From: "isaac buchwald" > but there is one more reason , why not to use it. > > If i write a package in ada , i would like to use in a different > invironment > without much ado , and without a separate layer that brings in a new > peril of quer functioning.