Chap. 10, pb 2 (again)

[akbar]

"Our class cannot handle a double digital as it needs two strikes. Work out a solution that will handle options with multiple parameters".

In one of the earlier posts of the forum, mj mentioned that the "short solution" to this problem is to use an array instead of a double to pass an arbitrary number of parameter. I assume this applies to the PayoffFactory::CreatePayoff(ID,double) and PayoffHelper<T>::Create(double) methods, along with the CreatePayOffFunction function pointer type definition.

However, using an array instead of a double means that an additional constructor, taking an array of doubles as argument, needs to be implemented for each of the classes of the PayOff inheritance hierarchy that have been developed so far in the book. This in order to be compatible with this new representation.
And there are a few of them: call, put, double digital, forward...

Above the fact that we clearly violate the open-closed principle, the solution appears far from short in the end. Is it the right approach, or is there a more elegant way of proceeding with mj's suggestion?
Maybe there is simply something that I've missed.
Thanks for you help in advance.

[mj]

the elegant solution is the one later in the book where we do template factories.

A solution that doesn't change the existing structure is not viable here.

[MoonDragon]

the elegant solution is the one later in the book where we do template factories.

Hello, is this part in the first version of your book (i only have this last)?

Regards

[mj]

this is in the second ed only.