Re: AdaYY wish list from current projects

[lutz@iks-jena.de (Lutz Donnerhacke)]

* Florian Weimer wrote:
>lutz@iks-jena.de (Lutz Donnerhacke) writes:
[Regenerating the access to an aggregate from an access to a component]
>> Very bad. I'd like to suggest a language feature in order to solve this.
>
>Perhaps general introspection? ;-)

Not yet. I'd like to obtain it from Objective-Ada.

>To be honest, I don't think that access-to-component variables can be
>added to Ada as transparently as it is possible in, say C++.  The involved
>offset might not be constant for types with discriminants, which makes
>implementations of this feature quite complicated.

That's why I want to add it to the compiler, because only it can decide how
to determine it or reject it completly for such reasons. I can only write my
generic package, distribute it, and fail a few years later in a complicated
production enviroment (usually a few hours before deadline).

>>>> Problem 2: Defining Byte_Order of record representations
>
>> Unfortunly I have to deal with memory mapped I/O (i.e. network cards)
>
>You didn't mention this...

Sorry, I shortend the problem a bit.

>> You miss the point. Providing such packages does not allow the compiler to
>> generate good maschine code.
>
>You need the conversion package anyway, at least that's my experience.
>Otherwise, your code is quite unportable, as you're passing around
>invalid values.

If my suggestion is part of the AdaYY specification, it would be perfectly
portable. Currently only packed bit fields can be used to address
representation issues correctly in a portable way.

>> >> Problem 3: Static expressions of discriminants in record representations
>
>> *Gna* And now remove the limitation, that the discriminants have to appear
>> first.
>
>Aha, this was the intent of your comment (I thought you were talking
>about the source code location).  Are trailing size specifies really
>common?  To me, they don't make much sense.
>
>> Even better: Try to write a program, which derivates the type from a pointer.
>
>Sorry, what do you want to do?

The problem escaped from a 'multiprotocol router'. Please try to map a IPv4
header incl. payload and IP-header options.
 
    head_len at 0 range 0 .. 3; -- or 4 .. 7 depending on the bit order.
    ...
    payload at head_len*4 range 0 .. packet_len - 32*head_len;