Re: Endianness independance

["Marin David Condic" <mcondic.auntie.spam@acm.org>]

This isn't really the proper domain for a programming language. There are
too many machine architectures, communication mechanisms and data
representations out there for a language to try to standardize them all. The
language wants to be targetable to a multitude of hardware, so it has to be
abstracted from underlying representation. By picking one form of endianness
over another or one form of floating point representation over another or
whatever other possible representations one might select, it would be ruling
out use of the language on a whole range of equipment. This isn't really the
place one tries to create interoperability.

Realistically, the answer is to assess the communications mechanisms needed,
establish a clearly defined protocol & representation and then build your
software to deal with that. Ada can be very good at handling the
representation selected, but it really can't define the representation for
you.

MDC
--
======================================================================
Marin David Condic
I work for: http://www.belcan.com/
My project is: http://www.jsf.mil/

Send Replies To: m c o n d i c @ a c m . o r g

    "Going cold turkey isn't as delicious as it sounds."
        -- H. Simpson
======================================================================

<Lionel.DRAGHI@fr.thalesgroup.com> wrote in message
news:mailman.6.1046445067.1343.comp.lang.ada@ada.eu.org...
> ...
> One big step towards interoperability and portability could be
> Endian-Portable record representation.
>
> Does someone knows if Norman H. Cohen proposal for Endian-Portable record
> representation clauses is examined within language revision?
>
> Lionel Draghi.