Re: Record representation : components order

[Stephen Leake <stephen_leake@stephe-leake.org>]

"Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr> writes:

> Going on in section 13, I did no see about record components order
> apart the “ at X range Y .. Z ” which directly specify it.
>
> But looking at some design in some place in the web, people usually do
> this way : define some component type with a size clause, and then,
> just use these type in some records, most of time, without using any “
> at X range Y .. Z ” . But to me, this seems to be unsafe, beceause
> components order is not guaranted to be that of the declaration.

You are correct.

If your application requires a specific component order, you must
specify the order in a record representation clause.

Anything else is compiler dependent.

Note that Ada 2005 allows specifying bit field placement using
endian-independent bit numbers.

-- 
-- Stephe