> It has to do with not having "hidden" input to a function.
Why would it be hidden? It's a default, customizable behavior. If you don't need to customize it you don't and there's no reason to task you with putting the method in the state which is going to be needed 9 times out of 10.
> and indeed if the default value is flipped in the header file the caller could change behavior with no code change at the call site!
And if the whole implementation is replaced by formatting your hard drive, the caller could change behavior with no code change at the call site!!
> Taking a line from the Python philosophy: "explicit is better than implicit."
You're probably misapplying/misunderstanding things, since Python is one of the languages making the most use out of default values and with extremely strong first-class support for them.
Why would it be hidden? It's a default, customizable behavior. If you don't need to customize it you don't and there's no reason to task you with putting the method in the state which is going to be needed 9 times out of 10.
> and indeed if the default value is flipped in the header file the caller could change behavior with no code change at the call site!
And if the whole implementation is replaced by formatting your hard drive, the caller could change behavior with no code change at the call site!!
> Taking a line from the Python philosophy: "explicit is better than implicit."
You're probably misapplying/misunderstanding things, since Python is one of the languages making the most use out of default values and with extremely strong first-class support for them.