× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. May 2010

Re: [SPAM 1]procedure parameter names

On Wed, May 19, 2010 at 9:58 AM, Rory Hewitt <rory.hewitt@xxxxxxxxx> wrote:
Personally, I still tend to use (up to 3) combinations of 3-character
multiples for variable names, e.g. RtnVal, RtnDtaLen, ElmNbr etc. Very
comprehensible (IMNSHO) and easier to write than ReturnValue,
ReturnDataLength, ElementNumber. But that's because I still use SEU and I
don't like to extend expressions over multiple lines where possible. Others
may (will!) disagree.

I think an argument can be made for common abbreviations used in
multiple places.

Stuff any experienced developer would recognize.

Your examples are perfect examples of such. I don't think anybody on
the list would have looked at RtnVal and read it any other way than
ReturnValue.

On the other hand, nobody but the OP would see DosTp and read DossierType

Charles

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.