Re: I'm facing an issue with: call to abstract procedure must be dispatching

[Serge Robyns <serge.robyns@gmail.com>]

On Tuesday, 8 December 2015 23:55:52 UTC+1, Jeffrey R. Carter  wrote:
> On 12/08/2015 01:21 PM, Serge Robyns wrote:
> > 
> > Before it was a limited interface and hence no record.  This reminds me I
> > haven't yet fully figured out when it is <b>best</b> use limited and when not
> > for my cases.  So far I can use limited as I don't need the assignment for
> > T_Store.  Likewise from you here I try to avoid access variable as much as
> > possible but at times I've no choice, well at least I use programming by
> > extension ...
> 
> If you don't need assignment because there will never be more than one of them,
> that's an indication that you don't need a type and a variable; you need a
> module. I suspect you think in terms of types because C++ only provides
> encapsulation and information hiding through its class construct. In Ada, your
> 1st thought when you want encapsulation or information hiding should be a pkg.
> 

How do I then pass the context?  I mean, now I pass the parameter around.  through global variables?  Also in the future I would like to have multiple "tasks" running, each with their "context", especially the db session.  I do believe these are good reasons for having a variable.