Re: Externalizing I/O

I have a basic first draft done.

Didn't you say your shop of "old school"? I didn't expect to see fully
free-form RPG, SQL DDL, binder source, etc. ;-)

Compiler directives in the service program prevent an existing program to

be re-compiled using the old getter/setter

Thanks for that reference to the compiler directives. It wasn't clear to me
how the itemsioTC program was avoiding a signature check after the itemsIO
*srvpgm was recompiled.

It still seems like itemsioTC could still run into numeric overflow errors
during runtime.

. This forces devs to use the new getter/setter whenever an existing
program is re-compiled.

Okay.

Like I said, I'm not happy with this.

At least the code is readable, and adds clarity and perspective to the
discussion. Thanks for sharing.


https://github.com/Justin-E-Taylor/ExternalIO-RPG