recio procedure calls. was IBM's RPG Strategy (was: Long Procedure Names)

On Thu, 24 Mar 2005 10:27:42 -0800, Tony Carolla <carolla@xxxxxxxxx> wrote:
> <snip>
> > the big advantage for me is that it is modular and procedure friendly.
> >  I can open a file in a procedure in one module, use it in another
> > module, then close it in a 3rd. What controls the show are the
> > parameters passed from one procedure to the next.  Which is what
> > modular programming is all about.
> </snip>
> 
> That's certainly an advantage.  I always try to avoid these problems
> by naming my F-spec entries with a prefix in service programs, and
> opening and closing them within each module independently.  But this
> doesn't solve the problem, it just makes more work really.
> 
> I wonder what would happen if a file was overridden.  Would the
> recio.h functions obey the override?

yup.  what they dont support are level checks ( at least I dont think
they do ).

the other problem with recio is the rpg programmer has to explicitily
close the file.  That is why Mr Farr should add data structure member
procedures and destructor procedures to RPG.  The file handle would be
stored in a data struct.  When the data struct is deallocated or goes
out of scope, the destructor procedure is run and calls the rclose
function.

-Steve