Encapsulating Construction Streamzine

good stuff here -

Scott Bain discusses using factories to prepare for complxity.

http://www.netobjectives.com/streamzines/CurrentStreamzine/index.html

I'd like to hear various opinions or general thoughts on the subject.

Greetings,
Dragonwell

 

[link9]

Actually, I think the factories part is a forgone conclusion in his presentation. What he's trying to get us to consider is encapsulating our constructors, which I do find a very interesting concept.

His point of separating the Use from Creation I think is also nice. If you're using factories, you're really already doing this unconciously, but it's always nice to see things articulated by those who have enough time to study these things. It will also help you to try and force the issue for a more pure practice.

I wonder, though... does it not stand to reason that an abstract class makes more sense than an interface in light of this pattern? The way that an abstract class can morph from a singular class all the way up through the chain is definitely an advantage over an interface.

This sort of goes against the way I've been directing our development of late (heavy interfaces), but... seems logical.

Thoughts?

-paul

The answer to getting answered -- faq855-2992