Re: Service program / procedure design and naming conventions

On Aug 4, 2017, at 4:50 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

My choice is to use F4 in the name. Thats pretty well understood by everyone, and if you make it the standard it will be picked up real fast.

Parm = SCRFIELD;
F4Org(Parm);
SCRFIELD = Parm;

should be all you need. Why would you need to test? I am not clear as to what "Do stuff" stuff there is ever to do? You're just filling the field for the user. Any validity checking would need to be done when the field is processed, regardless of whether the field was filled by F4 or from the keyboard.


On 8/4/2017 4:37 PM, Brian May wrote:

As to how to name it, you can ask 5 different developers and get 5 different answers.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD