×
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.
<snip>
Amazing thing is that there are actually people who use named constants.
Everyone I have ever known just puts AField = 52;. What the hell is 52 but
most places including the current the programmers would have a fit it they
had to identify a constant. I am the only person who ever did it.
</snip>
Alan,
I agree with your comment about the ambiguity of 'AField'. But that reminded me of when I first started learning Cobol some years ago (OK, a few decades ago). The instructors touted it as being "self-documenting" because one could have a 35-character field name. When I started using it (gave it up for Lent some time ago), I noticed that "veteran" Cobol programmers usually used 6-10 character field names. Heck, we had to hand-write programs on coding sheets back then! I doubt that I'll personally reach the 4096 character limit in RPG IV any time soon.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
