Re: Question: Combination of Access and Constraining

[Dmitry A. Kazakov <mailbox@dmitry-kazakov.de>]

On 20 Feb 2003 07:20:27 -0800, papand0pul0@yahoo.com (Papandopulo)
wrote:

>> Pointers are inherently bad. Why not:
>If they are ingerently bad why they are in
>the language ?

Because there are cases where they have no better alternative.
Nevertheless pointers is a source of countless problems.

>> function Fn (Arg : Tp) return Natural;
>I have to use access type here. Since this is
>simplified example. I have function accepting
>several such array arguments each of which is
>optional (null).

You can overload functions with different profiles.
 
>> But this is another type! Probably you meant a subtype:
>> 
>> subtype TpCon is Tp(1..1);
>Nope, now it says:
>warning: aliased object has explicit bounds.

Right, the above was not for pointers.

>> >So where I am going wrong here ?
>> 
>> You are mixing types and subtypes. If you want just to put a
>> constraint on a type, declare a constrained subtype.
>Gives warnings as I said before: variable with constrained subtype
>can't be aliased (any idea why?).

Because you need bounds to pass with. So if you really want pointers
(instead of letting the compiler to do all the dirty work for you),
then you could go like this:

   type Tp is array (Positive range <>) of Boolean;

   -- This will hold the constraint all the time
   type Tp_Rec (Length : Natural) is record
      Data : Tp (1..Length);
   end record;

   -- This value will serve as a default
   No_Data : aliased Tp_Rec :=
      (Length => 0, Data => (others => False));

    -- Anonymous access is safer
   function Fn (Arg : access Tp_Rec := No_Data'Access) return Natural;

   -- Put a constraint on it
   subtype TpCon is Tp_Rec (1);

   Arr : aliased TpCon; -- This is OK
begin
   Arr.Data (1) := True;
   Res := Fn (Arr'Access);
end Test;

---
Regards,
Dmitry Kazakov
www.dmitry-kazakov.de