initialization approach for STM32.Button about ada_drivers_library HOT 3 CLOSED

I agree we should just add a precondition here, that would allow testing that everything is fine in debug mode, and remove the overhead in production mode. That's clearly what preconditions are for, so I'm all for it.

I wouldn't want to have the initialization performed during the elaboration because this would be inconsistent with other packages whose initialize procedures have user-defined parameters and so cannot be performed automatically.

from ada_drivers_library.

I agree as well. We should standardize the board features packages (LEDs, buttons, screen, gyro, features of expansion boards, etc.) to have a set of common sub-programs:

type Init_Status is (Init_Ok, 
                     --  When everything is ok

                     Init_Not_Available,
                     --  When the feature is not available, for instance if the extension board is not plugged-in

                     Init_Error);
                     --  When everything went wrong...
procedure Initialize return Init_Status;
function Initialized return Boolean;

from ada_drivers_library.

Done.

A common initialization would be useful.

from ada_drivers_library.