| 114 |
|
the problem of creating objects without specifying the exact class |
| 115 |
|
of object that will be created. Factory method is typically |
| 116 |
|
implemented by delegating the creation operation to the subclasses. |
| 117 |
< |
Parameterized Factory pattern where factory method ( |
| 118 |
< |
createIntegrator member function) creates products based on the |
| 119 |
< |
identifier (see Scheme.~\ref{appendixScheme:factoryDeclaration}). If |
| 120 |
< |
the identifier has been already registered, the factory method will |
| 121 |
< |
invoke the corresponding creator (see |
| 117 |
> |
One of the most popular Factory pattern is Parameterized Factory |
| 118 |
> |
pattern which creates products based on their identifiers (see |
| 119 |
> |
Scheme.~\ref{appendixScheme:factoryDeclaration}). If the identifier |
| 120 |
> |
has been already registered, the factory method will invoke the |
| 121 |
> |
corresponding creator (see |
| 122 |
|
Scheme.~\ref{appendixScheme:integratorCreator}) which utilizes the |
| 123 |
|
modern C++ template technique to avoid excess subclassing. |
| 124 |
|
|