Re: Instantiating package problems

["G.B." <bauhaus@futureapps.invalid>]

On 04.01.16 01:30, Andrew Shvets wrote:
> Ok, I think I understand.  In Ada, every vanilla package imports all of the public functions/procedures to be used and can be thought of as static functions in C++.  However, I can create instances of different records in order to retain an element of state like I would in C++ when I create an object.
>

Consider this, just for some wording.

with Energy, Physics;

package Named_Things is

    function Consumption return Physics.Mass;
    -- equivalent of total energy transformed by traffic.

    type Car is private;

    procedure Method_1
      (The_Object : in out Car;
       Amount     : in     Energy.Fuel);

    function Method_2
      (The_Object : in Car)
      return Physics.Velocity;

    type Roadkill is
      (Squirrels, Cats, Rat, Opossums, Raccoons, Dogs, Deer);

    procedure Hit (Object_A : Roadkill; Object_B : Car);
    --  adds to goods consumed by traffic.

private

    Total_Consumption : Physics.Litres;
    --  burned by all cars, cf. Method_1, also equiv. Hit

    type Car is record
       Fill  : Energy.Fuel;
       -- ...
    end record;

end Named_Things;

Subprograms Method_1 and Method_2 belong to the primitive operations
of type Car, declared next to it as primitive subprograms. All three,
the type Car and its primitive subprograms, are declared in package
Named_Things.
Creating an object of type Car,

   My_Car : Named_Things.Car;

gives an instance of the type Car, for state;
calling Method_1 and passing this instance as the first argument
makes Method_1 operate on this object (formally, on the type, I think);
additionally, the body of Method_1 may assign a new value to the
variable Named_Things.Total_Consumption.

However, the package also has the declaration of another type
and two more procedures. One of them is referring to both types
in its parameter profile, viz. Hit.