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,e3feb606f668a7c1 X-Google-Attributes: gid103376,public From: "David C. Hoos, Sr." Subject: Re: Why should hackers love Ada. (Re: Ada 95 based RTOS) Date: 2000/02/24 Message-ID: #1/1 X-Deja-AN: 589244043 Content-Transfer-Encoding: 7bit References: <88ilp7$bcm$1@nnrp1.deja.com> <38ADCA44.3B91BF6F@averstar.com> <88qli0$gvr$1@nnrp1.deja.com> <38B2A2A1.FDCDDFE7@honeywell.com> <88ugrd$7j7$1@nnrp1.deja.com> <890ght$bih1@ftp.kvaerner.com> <38B3EA94.E3AB4929@maths.unine.ch> <38B41432.88D7389F@quadruscorp.com> Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Complaints-To: abuse@earthlink.net X-Trace: newsread1.prod.itd.earthlink.net 951387316 158.252.122.142 (Thu, 24 Feb 2000 02:15:16 PST) Organization: Ada95 Press, Inc. MIME-Version: 1.0 NNTP-Posting-Date: Thu, 24 Feb 2000 02:15:16 PST Newsgroups: comp.lang.ada Date: 2000-02-24T00:00:00+00:00 List-Id: Vladimir Olensky wrote in message news:sb8gj38sr2a132@corp.supernews.com... > > Marin D. Condic wrote in message <38B41432.88D7389F@quadruscorp.com>... > > >But I suppose those who would hang the moniker "hacker" upon themselves > >really want assembly language - only without the inconvenience of having > >to learn a new one every time new hardware comes out. Hence the > >popularity of things like C with hackers. > > > > > There even exists HLA (High Level Assembler) project which is nothing > more than new variation of C. > Intention is to use it instead of different assemblers. > Are you confusing the term HLA with that of High-Level Architecture, described in the following paragraphs from the project website? http://www.sisostds.org/stdsdev/hla/ If not, where can one get information about High Level Assembler? The High Level Architecture (HLA) has been developed with the objective of providing a common architecture applicable across all classes of simulation to support simulation interoperability and reuse. The HLA is defined by the following three draft standards: Framework and Rules - IEEE Standard P1516: The HLA rules describe the responsibilities of federates (simulations, supporting utilities, or interfaces to live systems) and federations (sets of federates working together to support distributed applications). The rules comprise a set of underlying technical principles for the HLA. For federations, the rules address the requirement for a federation object model (FOM), object ownership and representation, and data exchange. For federates, the rules require a simulation object model (SOM), time management in accordance with the HLA Runtime Infrastructure (RTI) time management services, and certain required functionality and constraints on attribute ownership and updates. Federate Interface Specification - IEEE Standard P1516.1: In the HLA, federates interact with an RTI (analogous to a special-purpose distributed operating system) to establish and maintain a federation and to support efficient information exchange among simulations and other federates. The HLA interface specification defines the nature of these interactions, which are arranged into sets of basic RTI services. Object Model Template (OMT) Specification - IEEE Standard P1516.2: The HLA requires simulations (and other federates) and federations to each have an object model describing the entities, not necessarily platform entities, represented in the simulations and the data to be exchanged across the federation. The HLA object model template prescribes the method for recording the information in the object models, to include objects, attributes, interactions, and parameters, but it does not define the specific data (e.g., vehicles, unit types) that will appear in the object models.