RE: Full Free RPG and modification marks

I expected some discussion about this but this far exceeded my expectations.

I have been entertaining the thought of writing some 'full-free' code (I will soon) (might as well have full-free programs mixed in with the RPG36 programs, lol). Just had some questions like this and thought this is great place to ask the question. Sometimes the 'books' just don't have practical experience, that a group like this will have.

I think the simple answer is the mod mark/comments will be on the right after the //.
Bigger question is what are the rules, and that is a personal/company standard.

P.S.
I am one of those people that read all of the post (when time permits) of several forums and very rarely post something. The education is priceless. I do not know how many times a co-worker will ask a question and I will say I just read on the forum...
I realy appreciate all of you and your thoughts. Keep up the good work. It is priceless.

Kerwin



-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Wednesday, October 02, 2019 5:13 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Full Free RPG and modification marks

Kind of thought maybe that was the case!

Cheers
Vern

On 10/2/2019 4:03 PM, Booth Martin wrote:

I misunderstood.  I thought he was starting from 100% fixed-form

On 10/2/2019 3:51 PM, Vernon Hamberg wrote:

Booth

You cannot go to full-free in a piecemeal fashion - that code in line
1 position 1 means the entire source starts in position 1 and is
free-form from 1 to whatever the record length is.

Without the str-start-free at the start, your code is limited to
position 8-80 or so.

You will not be able to start calculations in position 1 unless you
use the star-star-free marker.

Regards
Vern

On 10/2/2019 1:57 PM, Booth Martin wrote:

My first reaction is: Why jump off the end of the pier; no need to
go to full-free cold turkey?  Take your time, just do the C-spec
free to start with?  Maybe convert an existing program with RDi's
conversion tool and see how it treats your current documentation
process?  I suspect you will be pleasantly surprised.