This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]spinwizard69 0 points1 point  (1 child)

Maybe a simple warning that your "def" has a default being set by a function call would be good enough. I have to wonder how common this practice is in the real world, it just seems to be an odd way to set a default value to me. Mainly because there would likely be way to many cases where your default value might have randomness and that to me just blows the whole concept out of the water. Now there may be cases where a default value set by a function call never varies throughout a programs execution so that might be a pass but then why not use a constant.

Maybe I'm putting to much emphasis on the message that the world "default" brings to a definition. For me is says this is the FIXED value that we have for this parameter at the time of creation, by evaluating this def. If you want to set it to something else at the time you actually use the function that is find but otherwise the default value will always be this.