× 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. June 2005

Subprocedure Naming Conventions

I realize everyone has there own naming conventions or shop standards when naming subprocedures but I'm wondering as I create more subprocedures that are being 'exported' to other modules and these modules are being bound to programs and service programs if others on this list have some tips on 'gotchas' when naming subprocedures.
I've been using the '...' on the D spec to get past the 14 character limit and trying to have meaningful subprocedure names but I have that feeling that one day I will start to have the same subprocedure name in different modules............. 

Am I missing something basic here? Which won't be the first time..........:}

Thanks
Andy

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.