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


  1.  Home
  2. RPG400-L
  3. July 2003

Re: Free form code suggestion

John Taylor wrote:
From: Hans Boldt

That's not a bad idea. If we ever get free-form F, D, I, O, and P specs, it's not unreasonable to expect an option to assume /FREE and /END-FREE around the code.



Hans,

I'm probably missing something obvious, but why can't this be done even
with the existing fixed specs? If the control spec (ie:
sourcetype(*FREE) ) is set to free, then the compiler should assume that
all eligible source statements (currently only C specs) are coded in
free form.
...

OK, I get your point. Theoretically, the compiler could assume that any spec with blanks in positions 6-7 is a free-form calc spec. That's certainly doable, and if I recall correctly, I believe it was considered during V5R1 development. I believe the idea was rejected to discourage the mixing of fixed and free-form calcs, which, if allowed, would wipe out much of the benefit of free-form coding.

Cheers! Hans



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.