Re: Restrictions on compilers for Microsoft's .NET project

[Kilgallen@SpamCop.net (Larry Kilgallen)]

In article <3c680086@pull.gecm.com>, "Martin Dowie" <martin.dowie@nospam.baesystems.com> writes:
>> Note that this says that non-overlapped variants are ok. Ada only
>> allows non-overlapped variants.
> 
> er, shurely shome mishtake?...
> 
> it does allow them to be overlapping (via 'Size or a rep spec) but
> e.g.
>    type A_Variant (Value : Foo := Foo'First) is record
>       case Value is
>          when Bar1 =>
>             Int : Integer;
>          when Bar2 =>
>             Bool : Boolean;
>       end case;
>    end record;
>    for A_Variant'Size use 64;
> 
> but you do have to make a positive decision to do it and to do
> and you can't just change to the other variant without again
> doing something explicit (e.g. uncheck conversion, or a whole
> record assignment).

Certainly I am not expecting to be able to change variants on the fly,
but I have a lot of code that receives an access value denoting a
record and I have to check the value of a discriminant to determine
which fields of the record are available to me.  If I get it wrong
Compaq Ada will detect my error just as surely as it will detect an
out-of-range value of the discriminant.  Those possibly-present
fields from various variants are located at the same offsets as
each other.

The Microsoft publication I quoted described this as "unsafe".  Is
this prohibited by .NET ?  Is it allowed in Ada95 as in Ada83 ?