Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Unironically: For in-house scripts and toolboxes where I want to set stuff like input directory, output directory etc. for the whole toolbox, and then just run the scripts. There are other easy solutions of course, but this makes it really quick and easy to just run the scripts when I need to.
I don’t get it either. Why would you ever feel the need for them to begin with?
Unironically: For in-house scripts and toolboxes where I want to set stuff like input directory, output directory etc. for the whole toolbox, and then just run the scripts. There are other easy solutions of course, but this makes it really quick and easy to just run the scripts when I need to.
But those would be constants, not variables.
I typically don’t declare them as such - bring the pitchforks!
Everything’s a variable if you’re brave enough.
My
void*
doesn’t care about yourconst
!In software that’s already badly engineered. Either you do the work and refactor everything, or accept it’s probably not worth all the effort.