× 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: procedure parameter names

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Simon Coulter


Likely reason is copying from an OO practice. Arguments are
indefinite articles but variables used are definite articles
(recall your Grammar lessons).
C EVAL theDate = aDate

Our variables are in French, so that would translate as :
C EVAL laDate = aDate

Which makes no sense.

I could understand :
D UneDate D DATFMT(*ISO) CONST

But then we would also have :
D UnJour 2 N 0

Idea: I shall propose the prefixes <Un or Une> instead of <A> or <An>!
Problem : For <Table Name or nom de table> Do I use UneTabNm or UnTabNm?


As for the rest of your append ... I'll just hold my tongue.
What a cop out. I was counting on you, Simon. I suspect it's the short names or the use of data structures and I don't like it either but I have to live with it. If long parameter names were permitted, shouldn't they still conform to some kind of naming convention?

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.