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,3c42d4793dc714ed X-Google-Attributes: gid103376,public From: Laurent Guerby Subject: Re: Pro*Ada and Gnat Date: 1997/03/03 Message-ID: #1/1 X-Deja-AN: 222720930 Sender: guerby@boole.enst-bretagne.fr References: <5f9hlt$7j9@hetre.wanadoo.fr> Organization: ENST de Bretagne, Brest FRANCE Newsgroups: comp.lang.ada Date: 1997-03-03T00:00:00+00:00 List-Id: Rosen.Adalog@wanadoo.fr (J-P. Rosen) writes: > We have been unable to use Pro*Ada (Oracle) with Gnat. Apparently, > Pro*Ada uses heavily unchecked_conversions between pointers and > adresses, and other doubtful features; has anyone succeded to use > Pro*Ada with Gnat ? Two GNAT features are of a great help in this kind of situation: - Compile time warnings about Unchecked_Conversion between types with different sizes, - Size representation clause on access types. Example: type P is access String; -- by default fat (double) pointer with GNAT for P'Size use Integer'Size; -- force thin pointer function F is new Unchecked_Conversion (P, Integer); -- no more warnings ;-) -- Laurent Guerby , Team Ada. "Use the Source, Luke. The Source will be with you, always (GPL)."