|
I get the impression that you do not consider the long name capability either neccessary or desirable. I agree that long names for the sake of long names is unproductive and can make code harder to read, rather than easier. On the other hand, there are times that restricting your name to 6, 10 or 12 charcters does the same. I rarely go over 12, but there are rare occasions when I use 15-20 charaters because it causes the code to be easier to understand. Joe Teff >Here's an example: > >-------------------------------------------------------------- >H nomain > >D Really_long_but_not_necessarily_meaningful_procedure_name... >D pr 1a >D parm1 1a value > >P Really_long_but_not_necessarily_meaningful_procedure_name... >P b export >D Really_long_but_not_necessarily_meaningful_procedure_name... >D pi 1a >D parm1 1a value >C return parm1 >P Really_long_but_not_necessarily_meaningful_procedure_name... >P e >-------------------------------------------------------------- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.