More documentation of terminology...
Standardizing a lot of naming conventions at work, for messages and such.
You have things like camelCase and PascalCase, but none of them really deal with underscores.
If you have a module XXX and a class RandomClassName, our 'defacto' convention shows that you name the error message "The file you were searching for was not found." as:
XXX_RandomClassName_FileNotFound
In effect, PascalCasing the salient part of the message so it can be reused.
A recent perturbation in the Force lead some names to be written up as:
XXX_Class_RandomName_File_Not_Found
Reading these outloud has led me to a new *Case name....
...Shat_Ner_CASE
You have things like camelCase and PascalCase, but none of them really deal with underscores.
If you have a module XXX and a class RandomClassName, our 'defacto' convention shows that you name the error message "The file you were searching for was not found." as:
XXX_RandomClassName_FileNotFound
In effect, PascalCasing the salient part of the message so it can be reused.
A recent perturbation in the Force lead some names to be written up as:
XXX_Class_RandomName_File_Not_Found
Reading these outloud has led me to a new *Case name....
...Shat_Ner_CASE