Re: constructor in abstract tagged types

["Randy Brukardt" <randy@rrsoftware.com>]

"Daniel" <danielnorberto@gmail.com> wrote in message 
news:0ca05176-a819-4e9a-8c6c-3a0c1f32f964@googlegroups.com...
...
>Option 2:
>
>  return Son'(Father with
 >              Skate =>True);
>
>Problem: i cannot initialize Father or call any kind of constructor of 
>Father
>becouse compiler don't let me make any kind of function of a abstract 
>tagged type.

Correct. But that's what you declared in this case, so I would assume that 
you want to manually initialize all of the components.

If you have proper default values for the components, why not declare the 
Father type that way?? Uninitialized stuff often leads to trouble anyway.

That is:

  type Father is abstract tagged record
     Years : Natural := 0;
     field1 : Natural := 0;
--    .....and 15 more fields
  end record;

If you *don't* want this sort of default value, then it only makes sense to 
initialize all of the components when the object is first created. (Or you 
could define a procedure to do it, as Dmitry showed. But you lose 
completeness checking when you do that.)

                                    Randy.