Re: Strings with discriminated records

[Mehdi Saada <00120260a@gmail.com>]

Let's go half and half: how about making subtype indication in object renaming simply optional, and allow it for compatibility and in case of ambiguity ? A pragma would suffice if it doesn't exist yet (just wondering).

I can see myself how renaming is broken:
Some constraints in subprograms profile are taken in account, and some are not.
The compiler will enforce this constraint:
Function KI (JJ : in INTEGER := 5) return Integer is (JJ);
function KKI (JJ : in Positive) return Positive renames KI;
then put_line(KKi(-5)'img) will cause warnings.

But this is ignored:
procedure MMI (JJ : in Integer) renames MM;, the subtype in MM's declaration is used, and this is ignored too: 
declare
   procedure KI (JJ : out Integer) is
   begin
      JJ := -5;
   end KI;
   procedure KKI (JJ : out Positive) renames KI;
   M : Positive;
begin
   KKI (M);
end;
Then you really obtain a M with a value out of range. What the fuck ? This is the worst thing and type security breach I saw in Ada until now. Fixing this in the next version is more important that adding new features, and it's worth incompatibilities.