Yeah, well, OK - I can see the "$" issue. $Rv or $Rc (ReturnValue or ReturnCode) are better.

I do try to limit my use of the $, and also follow a set of "rules" for my coding projects:
  • Global vars are $ALLCAPS
  • Local vars are $MixedCase
  • Macros are treated as globals, since they are the same regardless of being in a function or the main code, and are @ALLCAPS
  • Commands & Functions are MixedCase, and all operators, commands, functions, arguments/parameters, variables and values are separated by a space. This helps in formatting with PostPrep when long-line wrapping is enabled.
  • Any local var defined in a function is prefaced with a "_", as in $_VarName. This avoids conflicts in naming with other UDFs when explicit is not enabled, and especially conflicts with global vars.
  • Variable re-use is limited to those capturing return values, and those used to index/increment a pointer.
  • While I don't use strict Hungarian notation, I do preface most arrays with "a" - as in $aComputers for an array of computer names. Since Kix uses variants (variables that can hold anything) the notation loses some value. I often, however, reference variables that must hold a specific type of data that's been cast, like $dCTime for a double-precision CTime representation of the current date/time. This is one rule that - for me - can be bent and twisted to suit my needs and my mood. I have too much code and too many UDFs where this isn't followed to get strict about it now.
The real point is to find a style that works for you and presents well to others. Develop that style and stick with it. It may change and evolve over time, but it shouldn't waver constantly.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D