Back to General and Gameplay Programming

Factory Pattern: Extensibility Question

Neutron · 2003-02-05T08:30:11

I read about the benefits of the Factory Pattern (simplified Factory without subclassing (via static method), Template Method) and they seem quite obvious to me. Factory Patterns, for example, are said to improve extensibility because object creation is centralized and therefore you don't have to worry about other parts of the code when you add new types. However, I can't think of any good example where extensiblity can be an issue when introducing new types without using the factory pattern. The only case that came into my mind is that when using a newer derived component and prefering it over the "obsolte" component it can be convenient having the construction code in one place because you'd only have to change the constructor call of the new type once - in the factory. I assume that this is an extreme case - maybe you can give me better examples. I'd be very grateful for any illustrations. [edited by - Neutron on January 21, 2003 12:25:47 PM] [edited by - Neutron on January 21, 2003 12:27:00 PM]

General and Gameplay Programming Programming

Started by Neutron January 21, 2003 11:23 AM

10 comments, last by Neutron 21 years, 2 months ago

Anonymous

February 04, 2003 11:52 AM

the other ap used the "if/else"-code as an example for bad code and how it would be refactored using the factory pattern. he never went into the implementation of the factory itself.