Behavioral Design Patterns in C++ - Non-Member Strategy Pointer

The video tutorial discusses the use of strategies in programming, focusing on how strategies can be injected into contexts either through constructors or setters. It highlights the flexibility of not always needing to make strategies members of a class, using examples like spreadsheet export and dynamic arrays. The tutorial explains when it is beneficial to pass strategies as arguments rather than class members, such as in the case of lock policies in dynamic arrays. It also covers the use of stirred functions in arrays and concludes by emphasizing the ease of specifying strategies as function arguments.

What is the advantage of passing the format pointer directly in the export function instead of making it a member of the data model?

Why is it suggested to make the lock policy a member of the class when protecting methods from being accessed by multiple threads?

In the context of the dynamic array example, why is it unnecessary to make the stir function a member of the class?

What is the significance of checking for a valid target before invoking a function in the print method?

How can the strategy be specified when printing the data of the array in a specific format?