StDoodle
Minion
Title pretty much sums it up. The two main reasons are:
1) I like to write a few helper functions to be used by the "public" functions in my imported scripts that could easily cause errors if they weren't used "correctly." Generally, I try to code them so that this won't happen, but many times it's a significant difference in coding to make such a function near-foolproof vs. making it foolproof for how it's being used by other "public" functions in the script.
2) It would be nice to have such "private" functions hidden in the list of functions shown with a "verify" cli command.
If this would be something that could be added as a feature, I would be happy with pretty much any formatting requirement for the declaration of functions as private, from something as simple as adding "private" before the declaration, to as complex as some weird string of characters having to occur at a certain point in the function name.
1) I like to write a few helper functions to be used by the "public" functions in my imported scripts that could easily cause errors if they weren't used "correctly." Generally, I try to code them so that this won't happen, but many times it's a significant difference in coding to make such a function near-foolproof vs. making it foolproof for how it's being used by other "public" functions in the script.
2) It would be nice to have such "private" functions hidden in the list of functions shown with a "verify" cli command.
If this would be something that could be added as a feature, I would be happy with pretty much any formatting requirement for the declaration of functions as private, from something as simple as adding "private" before the declaration, to as complex as some weird string of characters having to occur at a certain point in the function name.