|
On Thu, 24 Mar 2005 13:21:04 -0600, Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote: > I would think this is also far more readable than passing file handle around > or using data export to get the file handle. Lim, you mentioned in your first post that you like seeing all the fspecs at the top of the module as a way to know all the files used in the program. By the same token, it would be a good thing to look a the parm list of the procedure to get a good idea of what the procedure does. I would argue that modularity = readability. -Steve > > -----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> > > -- > This is the RPG programming on the AS400 / 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. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.