-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify the true/false settings in our code #625
Comments
+1 Do we have tri-states? Like Yes/No/Auto? Or Yes/No/Unset? |
When there is one or more common functions it can be enhanced as needed to test for as many states as needed like yes/no/auto/unset/default/... I wonder if it is possible to test that common functions are actually used everywhere? In other words: How to find all places in the code that would need to be unified? |
There is no need to change all code at one moment - whenever, we feel the need (or come across one piece of code) we can change it... |
You are right. Same reasoning as my own comment ("can be enhanced as needed"). Somehow I failed to apply my own reasoning to my own question ;-) |
Function seems to work. It is now just a question of using it when we come across a script which uses a non standard test for true/fasle. |
We have too many ways of defining a variable to be true of false, e.g.
Maybe, we better create a simple function to unify this?
Feedback welcome...
The text was updated successfully, but these errors were encountered: