Bob Cozzi Wrote:

>> The /FREE /end-free thing is consistent with /EXEC SQL /COPY, /INCLUDE,
>> etc.
>> But if, in a future release, IBM wanted to support the ability to have
>> /FREE as the default for the compiled source member, they could simply
>> add a KEYWORD to the header specification:
>>
>>
>> .....H  OPTION(*FREEFORMCALCS)
>>
>> Or similar.
>> Then /FREE would NOT be needed, and ALL calcs would implicitly be in
>> free format.  Then, the only way to NOT have free format would be, say
>> to allow me to put a C in column 6.  Hence, this subtle change would
>> allow you to code free format starting, effectively in column 7.
>>
>> .....C                   MOVE  A           B
>>          If   A = B;
>>            C = A * 100;
>>          else;
>>            C = A * 50;
>> .....C                   SETON                         LR

I agree with this except for one thing.  Why would there be a need for an H 
spec.
Couldn't the compiler assume that any code that does not have a spec letter in 
position 5
or * or / in position 6 to be free format.  I personally like free format but
think the /free /end-free clutters up the code whether it is jumping in and out
of free format or not.

Seth Shields
Julius Blum Inc.



This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.