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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,bd3300f3a56e7f45 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-03-19 05:11:01 PST Path: archiver1.google.com!news1.google.com!news.glorb.com!newsrout1.ntli.net!news.ntli.net!newsfeed.stueberl.de!newsr1.ipcore.viaginterkom.de!news-peer1!btnet-feed5!btnet!news.btopenworld.com!not-for-mail From: "Martin Dowie" Newsgroups: comp.lang.ada Subject: Re: different compilers: different standard types????? Date: Fri, 19 Mar 2004 13:10:08 +0000 (UTC) Organization: BT Openworld Message-ID: References: NNTP-Posting-Host: host81-129-22-113.in-addr.btopenworld.com X-Trace: sparta.btinternet.com 1079701808 6862 81.129.22.113 (19 Mar 2004 13:10:08 GMT) X-Complaints-To: news-complaints@lists.btinternet.com NNTP-Posting-Date: Fri, 19 Mar 2004 13:10:08 +0000 (UTC) X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MSMail-Priority: Normal X-Priority: 3 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Xref: archiver1.google.com comp.lang.ada:6442 Date: 2004-03-19T13:10:08+00:00 List-Id: "Riccardo" wrote in message news:c3e7qn$2oe$1@e3k.asi.ansaldo.it... > My problem was of course not to define new types but to use the same type > (with the same source files!) on both the consoles (a Sun Spark and an Alpha > Digital ). > > So in defining new types I have to be sure that I don't have to manage > different source codes. > > I'm looking for a sort of pragma that should help me to share the needs of > the two implementations (as the "conditional compilation" in C). > > I saw that the pragma System is a deprecated one. > > Is there something useful that allows the operation? But surely the solution to your problem is to simply not use predefined types? Define your own with the range you require or use the type in package Interfaces.