4 deleted 1 character in body
source | link

I am not aware of a specific name for this, but I guess it is worth to mention that the problem you describe istis just the problem of finding the best compromise for the scope of such a parameter:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, when it leads to lots of repetitive parameter lists in call chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

I am not aware of a specific name for this, but I guess it is worth to mention that the problem you describe ist just the problem of finding the best compromise for the scope of such a parameter:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, when it leads to lots of repetitive parameter lists in call chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

I am not aware of a specific name for this, but I guess it is worth to mention that the problem you describe is just the problem of finding the best compromise for the scope of such a parameter:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, when it leads to lots of repetitive parameter lists in call chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

3 added 22 characters in body
source | link

I doam not think there isaware of a specific name aboutfor this, but what you are describingI guess it is worth to mention that the problem you describe ist just the problem of finding the best compromise for the scope of such a variableparameter:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, which is indicated by the cumbersomewhen it leads to lots of repetitive parameter lists in call-chains chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

I do not think there is a specific name about this, but what you are describing is just finding the best compromise for the scope of a variable:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, which is indicated by the cumbersome call-chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

I am not aware of a specific name for this, but I guess it is worth to mention that the problem you describe ist just the problem of finding the best compromise for the scope of such a parameter:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, when it leads to lots of repetitive parameter lists in call chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

2 deleted 5 characters in body
source | link

I do not think there is a specific name about this, but what you are describing is just finding the best compromise for the scope of a variable:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, which is indicated by the cumbersome call-chains

  • so as a trade-off, you might consider tocan often make thesuch a parameter a member variable in one or more classes, and that is what I would just call proper class design.

I do not think there is a specific name about this, but what you are describing is just finding the best compromise for the scope of a variable:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, which is indicated by the cumbersome call-chains

  • so as a trade-off, you might consider to make the parameter a member variable in one or more classes, and that is what I would just call proper class design.

I do not think there is a specific name about this, but what you are describing is just finding the best compromise for the scope of a variable:

  • as a global variable, the scope is too big when the program reaches a certain size

  • as a purely local parameter, the scope might be too small, which is indicated by the cumbersome call-chains

  • so as a trade-off, you can often make such a parameter a member variable in one or more classes, and that is what I would just call proper class design.

1
source | link