Re: Abstract methods in ADA95

[Jim Rogers <jimmaureenrogers@worldnet.att.net>]

Programmer Dude wrote:

> SteveD wrote:
> 
> 
>>When is the last time you heard somone talk about a "Crapper"?
>>
> 
> Quite recently.  I use it all the time.  ;-)
> 
> On topic.... To be honest, I dislike the term "subprogram" to mean
> a *piece* of a complete program.  To me "program" implies a sense of
> completeness I don't find in a sub-routine/function/method/whatever.
> As an Ada nuub, I'm still in the mental translation "subprogram" ==
> "function" phase, and it's ever so slightly jarring.
> 
> (Back off topic....In the language I designed I called'm "Actors".
> They perform Actions. :-)
> 
> 

In the Ada sense they are called subprograms because procedures and
functions are different in Ada. This also distinguishes the set of
procedures and functions from tasks.

The sets of "actors" in Ada can be grouped in interesting ways.

subprograms - the set of non-protected procedures and functions
protected operations - the set of protected functions, protected procedures,
                        and protected entries
tasks

Grouping all these "actors" under a single set such as methods, subroutines,
or subprograms is not useful. Each grouping has its own set of interface
and usage rules.

Subprograms can be called by other subprograms, tasks, and protected operations.
Tasks can only be "called" through their entries.
Protected operations only work on protected objects and always imply mutual
exclusion locking.

If you get very general and try to group all these entities together you will
obscure the very real differences. I do not think such obscurity is useful.

Jim Rogers