Re: How to return an empty aggregate

[george.priv@gmail.com]

On Apr 3, 5:09 am, Maciej Sobczak <see.my.homep...@gmail.com> wrote:
> On 3 Kwi, 07:02, george.p...@gmail.com wrote:
>
> > Sorry, maybe I am missing something but what's practical sense of
> > having non-abstract null record implementation of interface(s)?
>
> Stateless strategy patterns?
> Factories?
> Finite state machines (no need for state within state)?
>
> Actually, most of the design patterns I can think of make sense in
> some stateless form, because the concrete *type* of the object is
> often enough to play the role of a state at some higher level.
>

Maybe I put my question incorrectly.  I did not mean challenge those
concepts in purity.  Good example is a factory.  Should it have a
mechanism to register-unregister itself?  Would it imply either
deriving from something like Finalization.Controlled or the other
root, or putting some meat into the object itself?  In addition such
objects make sense in singleton form and likely involve some sort of
guarding mutexes or be implemented as protected or tasks.  BTW in C++
empty factory class will be fine due to implied constructor/
destructor.

> Interfaces are more about operations than about data.
>
> --
> Maciej Sobczak *www.msobczak.com*www.inspirel.com