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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,aebfabc06e1feb33
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-10-19 18:19:15 PST
Path: 
 bga.com!news.sprintlink.net!sundog.tiac.net!wizard.pn.com!satisfied.elf.com!news.mathworks.com!yeshua.marcam.com!zip.eecs.umich.edu!newsxfer.itd.umich.edu!gatech!swiss.ans.net!cmcl2!thecourier.cims.nyu.edu!thecourier.cims.nyu.edu!nobody
From: dewar@cs.nyu.edu (Robert Dewar)
Newsgroups: comp.lang.ada
Subject: Re: Interface GNAT with Oracle
Date: 19 Oct 1994 09:23:15 -0400
Organization: Courant Institute of Mathematical Sciences
Message-ID: <3836k3$fm0@gnat.cs.nyu.edu>
References: <389@sphinx.CSS.GOV>
NNTP-Posting-Host: gnat.cs.nyu.edu
Keywords: Oracle GNAT
Date: 1994-10-19T09:23:15-04:00
List-Id: <comp.lang.ada>

I don't know anything specific about GNAT and ORACLE working together, but
an important thing to remember is that the GNAT calling sequence is exactly
the C calling sequence, and the GNAT datatypes correspond to the C
datatypes (e.g. int = integer, char = character). Access types and
address values in GNAT look like C pointers EXCEPT for access types for
unconstrained arrays, which are quite different, so avoid their use in
low level interface code.