> Where the compiler puts on stack the default value, whenever the function call doesn't include it. So if a dynamically linked library uses default values, an

> Where the compiler puts on stack the default value, whenever the function call doesn't include it. So if a dynamically linked library uses default values, and you make use of them, and the dynamically linked library decides to change its default values (e.g. a crypto library switches to more secure defaults), you don’t get the update until you recompile your own code. That doesn’t sound great. Isn’t it C# which uses this strategy, of embedding the defaults in the caller? PS: I don’t think C is defined in terms of stack, and modern calling conventions use registers for at least the first few arguments.