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




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

I'm curious why someone who is about the task of setting
standards would declare "I have to live with it." Doesn't
the practice of standards setting involve/include not living
with the past standards?

I agree with you, Dennis, but I'm not setting any standards. I've just been asked my opinion that's all. At the moment, thanks to Simon, I have a good reason for getting rid of names beginning with <An> but that's not gonna make a huge difference.

We've always used the same data dictionary. It's always been the same DDS file with 5 character names, 2 syllables of 3 and 2 characters respectivlely. When RPG4 came, we were able to import this file for all our variable/parameter declarations, eg
D ADosTy LIKE(Dictionnary_DOSTY)

So, noone has to think or search in able to declare the dossier type.

Unfortunately, the dictionnary has never evolved, which is probably why we are stuck with the short variable names. On the other hand, procedure names have become long and in my opinion misused eg :
D AcqDatDrnCmmAdh...
D PR N

Here we have 5 groups of 3 characters each one an abreviation of something.

Now, if I were to code
D GetLastCommandDate...
D PR N

I'd get my knuckles rapped. Now, if you've got any good advice on how to get things moving in the right direction, I'd be very grateful.


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.