Re: T'Interface attribute

[Eryndlia Mavourneen <eryndlia@gmail.com>]

On Wednesday, August 2, 2017 at 11:46:56 PM UTC-5, Randy Brukardt wrote:
> 
> P.S. And as always, explain the problem to be solved as well as the possible 
> solution. That is always necessary to understand the value of a proposal.
> 
> P.P.S. I personally have never seen a real-world example where an interface 
> actually helps. There's lots and lots of book examples and show examples and 
> so on, but in practice you end up with only a single implementation so there 
> really is nothing gained by involving a lot of dispatching calls. Ergo, I'm 
> against anything (new) involving interfaces. YMMV.

I use task interfaces in the case in which I have a basic task design that has certain core functionality and additionally may have any of a variety of other functionalities, too.  At the point at which I am ready to consolidate the interfaces into a specific kind of task, combining the interfaces, which already have declared the necessary entries (as procedures), becomes akin to building using Legos.

I find this kind of construction most pleasurable to design and implement.  It also is easy to understand.