Re: Why should hackers love Ada. (Re: Ada 95 based RTOS)

["David C. Hoos, Sr." <david.c.hoos.sr@ada95.com>]

Vladimir Olensky <vladimir_olensky@yahoo.com> 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.