Re: why private virtual function?
- From: "Alex Blekhman" <tkfx.REMOVE@xxxxxxxxx>
- Date: Sun, 16 Mar 2008 16:24:26 +0200
How do you think the article violates your pattern of thin
Because it makes it complex by making virtual function into
private part of
interface and not keeping all methods public?
Because it makes additinal methods, which are mere wrappers around
real workers. Sometimes it's useful, sometimes not.
If yes, I do not understand why you say in the way described in
the interface is not "thin". How do you define whether an
interface is "thin"
Example #1 in the article demosyrates "thin" interface (though
susceptible to possible modifications in the future). Example #2
demonstrates more stable interface, though all of its public
members are just wrappers.
- Prev by Date: Re: why private virtual function?
- Next by Date: Re: Impossible to get the sysuptime on windows 2000
- Previous by thread: Re: why private virtual function?
- Next by thread: Re: why private virtual function?