G'day Lotus1,
You could follow the convention used by Data::Dumper. It has a couple of screenfuls of "Configuration Variables":
$Data::Dumper::Indent $Data::Dumper::Trailingcomma $Data::Dumper::Purity ... lots more ... $Data::Dumper::Sortkeys $Data::Dumper::Deparse $Data::Dumper::Sparseseen
So that would suggest: $Data::GUID::Any::Uppercase.
That, however, is counter-intuitive. If the purpose is to choose lowercase, $Data::GUID::Any::Lowercase would, in my opinion, make a lot more sense. Default would be FALSE; set it to TRUE if you want lowercase.
I see you've already received conflicting advice; you may get more. There's really no convention for this; for instance, I've frequently seen $DEBUG. Perhaps the best advice is to make your own choice then use it consistently across your modules. Just to expand on the Data::Dumper example, I know I'd find it very annoying if I had to continually check the documentation to see whether I needed useQQ or useQq or UseQq or ... you get the picture: they all have the same format; in this case, Useqq.
— Ken
In reply to Re: when to capitalize package variables
by kcott
in thread when to capitalize package variables
by Lotus1
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |