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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, PLING_QUERY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b87bc683630619fa X-Google-Attributes: gid103376,public From: Daryl Siddon Subject: Re: HELP:Declaration in ADA?!! Date: 1996/04/18 Message-ID: <317708AE.48E3@cpmx.saic.com>#1/1 X-Deja-AN: 148282401 references: <4j65rr$fqg@soleil.uvsq.fr> <4kc5ti$1ir@comet2.magicnet.net> <4ulok5fn1m.fsf@zippy.frc.ri.cmu.edu> content-type: text/plain; charset=us-ascii organization: SAIC - Orlando - Advanced Distributed Simulation Technology II (ADST-II) Program mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.0 (Win95; I) Date: 1996-04-18T00:00:00+00:00 List-Id: Martin C. Martin wrote: > > > Tuyet-Tram DANG-NGOC wrote: > > > > >Hi there, > > > > >I have a stupid question to ask. > > >DOES SOMEONE KNOW HOW TO DECLARE LONG_INTEGER IN ADA? > > >All the books I've read here does not answer this metaphysical question, they > > >just take it as if everyone should know how to declare it. In a wonderful > > >book, I've seen how to declare LONG_REAL by typing: > > > type LONG_REAL is DIGIT 14; > > >But how to do it for LONG_INTEGER? > > >Can someone answers me pleeeeaaaase, i've a big and horrible project to finish > > >for very soon. > > Long_Integer may already be defined in your compiler; the ARM says > it's an optional type, but I think most compilers define it (at least, > if there are assembly instructions which would manipulate such an > integer directly). > > If not, you can define it this way: > > type Long_Integer is range -2_147_483_647 .. 2_147_483_647 > > Mind you, I think this will only work if there already is a 32 bit > integer type in your compiler, and if so it's probably already called > Long_Integer. > > Martin. The approach we used on a recent large scale production software development effort was to RESTRICT the use of the Standard types in application code, by declaring a uniquely named package "Project_Types" which had all low-level (compiler implementation defined) types. This project must ensure that future maintenance (20 years worth) will be relatively easy to adapt to new compliers. This "Project_Types" package localizes the changes needed when using a different compiler. All application types are based upon the "Project_Types" package. Typical types in "Project_Types" may be: type unsigned_integer16 is ... type unsigned_integer32 is ... type signed_integer16 is ... etc. Developers make specific decisions about the types their application code needs based upon the range of values, as opposed to "implementation defined" ranges (e.g. Standard.Integer). Disadvantage: The types in this package must be pinned-down very early in the project lifecycle, as any change/addition will necessitate a recompile for all client units. NOTE: As an entry criteria for Code Reviews, no Standard types are allowed; only those from "Project_Types". Prior to code being submitted to an "engineering build," scripts are run to scan for misuse. Advantage : It localizes the "compiler implementation defined" types, rather than throughout application code. Hope this helps. Daryl Siddon (Opinions only mine)