Problem with boost::bind, boost::function and boost::factory?

The bind function returns a two-argument functor because you bound the third and fourth parameters of your constructor to the placeholder values 1 and 2 However, you're storing the result in a zero-argument function object I found a reference from six years ago explaining that you can't omit parameters when you bind a function even if they're declared with default values I think you have three options: Provide actual int values in your call to bind instead of placeholders Change the declaration of f to indicate that it stores a two-argument function, and then always provide both values when you call it Bind the last two parameters to variables See Delaying constants and variables in the Boost. Lambda documentation. Then, you can set those variables to the same default values as the constructor declares.To use the default values, do nothing more.

To specify non-default values, assign values to those variables before calling f The last option will probably just make your code harder to read without much benefit, so prefer one of the first two options instead.

The bind function returns a two-argument functor because you bound the third and fourth parameters of your constructor to the placeholder values _1 and _2. However, you're storing the result in a zero-argument function object. I found a reference from six years ago explaining that you can't omit parameters when you bind a function, even if they're declared with default values.

I think you have three options: Provide actual int values in your call to bind instead of placeholders. Change the declaration of f to indicate that it stores a two-argument function, and then always provide both values when you call it. Bind the last two parameters to variables.

See Delaying constants and variables in the Boost. Lambda documentation. Then, you can set those variables to the same default values as the constructor declares.To use the default values, do nothing more.

To specify non-default values, assign values to those variables before calling f. The last option will probably just make your code harder to read without much benefit, so prefer one of the first two options instead.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.