RE: FW: IBM's RPG Strategy (was: Long Procedure Names)

I would think this is also far more readable than passing file handle around or 
using data export to get the file handle.

-----Original Message-----
From: Lim Hock-Chai 
Sent: Thursday, March 24, 2005 1:19 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: FW: IBM's RPG Strategy (was: Long Procedure Names)


I'm not sure why a module needs to close a file.  However, if application 
design calls for it, you can simply, on each procedure, add the following like 
of codes for files that it try to access:
if      not %open(MyFile)
open    MyFile
endif

or you are like me who trusts AS400 so much that I just do this:
open(e) MyFile

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Richter
Sent: Thursday, March 24, 2005 1:10 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: FW: IBM's RPG Strategy (was: Long Procedure Names)

<clip>
Lim, it also makes it easy for one procedure in a module to close the
file that another procedure has opened and is expecting to stay open. 
Not very modular!
<clip>