Re: Additional RPGLE Enhancement Requests

>> Bob Cozzi wrote:
>> 
>>The CONST keyword easily identifies the item as a constant. That stupid "C" 
>>in column what-ever-it-is should be optional, and NOT inserted into 
>>converted code. I my opinion
>
> Charlie Massoglia wrote:
> If Bob's suggestion is to eliminate the requirement for the "C" in whatever
> column if appears if the CONST keyword is specified I agree.  My point was
> if you code the "C" in whatever column,  you currently DO NOT NEED to code
> the CONST keyword.  You can just code the character value enclosed in quotes
> or the numeric value as is.  Just like in display file DDS, when you code a
> constant on a screen, you do not code the keyword, you just code the
> constant enclosed in quotes.

I'm not sure that I agree with this. I dislike the CONST keyword and remove 
them after converting a program. The "C", however, is an easy way to see what 
the field. If blanks weren't already used as meaning subfields, I would have no 
problem. Yes, if you look to the right, you can see the CONST keyword. But, if 
you are browsing through the code, looking in that column, it is easy to see 
where a data structure begins and ends, as well as, what are standalone fields 
and constants, IMHO.

Joe Teff
QDS
Bloomington, MN
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *