Re: Private primitive operations available to entire package hierarchy. Can it be done?

["Lucretia" <lucretia9@lycos.co.uk>]

<quote>
> Add(Some_Sizer, Self.Button'Unchecked_Access..­.);

Is this in the user code, or in the implementation of the interface? If
it's
in the implementation of the interface, do whatever you have to do. If
it's
in the user code, though, I'd claim that the Add routine is incorrectly

specified -- it should simply pass the Button_Type object and the code
*internal* to the binding should be creating the access types.
</quote>

Yes, that line would be in the user code as Add is a primitive to
wx.Core.Sizer.Sizer_Type.

<quote>
> and having all primitives take an access parameter as the controlling
> parameter.

That's awful. If you do that, you're requiring your user to do memory
management for you, rather than the other way around. They'll be forced
into
subpar syntax (explicit uses of aliased and 'Access), have runtime
accessibility errors, and other nastyness. And they would have no way
to use
the containers library do the storage management for them.
</quote>

What's awful? Using access parameters as the controlling type or just
using instances the way I have been doing?

I don't really see what you mean about forcing the user into handling
the memory management. subpar syntax? Dunno what that means :-/

<quote>
And the implementation of Add:


    procedure Add (Sizer : Sizer_Type; Button : Button_Type'Class) is
         My_Button : Any_Button_Access_Type := Button'Unchecked_Access;

         My_Sizer : Any_Sizer_Access_Type := Sizer'Unchecked_Access;
    begin
         -- Call the low level (C) routines:
         wx_Add (My_Sizer, My_Button);
         -- etc.
    end Add;

You might need to do some type conversions on the access types, but
that's
</quote>

I thought that it was considered bad to get the access of a parameter
in this way?