RE: Record name the same as the file name -- RPG400-L

Even more so that local files, I'd like to see the ability to share the I/O
buffer of a file between modules. 
For example:  Declare file CUSTMAST in MODA and do a READ to that file
somewhere in the main-line calcs or a subproc in MODA, then call a proc in
MODB and have that proc in MODB be able to see the input fields from the
read in MODA.
I can do this today with smoke, magic and mirrors, but it should be easier.
To make it easy, we'd only need the EXPORT and IMPORT keywords at the FILE
level, and Toronto to do the work under the covers. <g>


Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Hans Boldt
Sent: Monday, August 25, 2003 7:39 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Record name the same as the file name

Steve Richter wrote:
> Hans wrote:
> 
>>Allowing record names to be the same as file names would require a
>>major rewrite to the handling of files and records in the compiler,
>>with implications throughout the code, as well as the rules of the
>>language.
> 
> 
>>I'm not saying it can't be done. It's just that it involves one heck
>>of a lot of code change in the compiler, and the only advantage to
>>the RPG programmer is that she can avoid one RENAME on the F-Spec.
> 
> 
> how does that email expression of mock puzzlement go?  Is it "Huh?"

I usually write that as "Huh?!?".

> 
> RPG procs need to be improved so that file declares can exist within the
> scope of the proc, right?  Where a file can be declared at the proc level
> and auto opened and closed as the proc is entered and exited. ( just like
> the way files declared at the pgm level behave ) Also very useful would be
a
> file handle returned by the open of a file that can be passed from proc to
> proc and used for i/o against the open of the file the handle represents.

Local files? I agree that that would be useful functionality. File 
handles? That too would be quite useful. And like all other proposed 
enhancements, their usefulness would have to be weighed against the 
cost of implementation, and compared to other proposed enhancements.

> 
> Since procs already ( guessing ) have an automatic storage environment
that
> they operate in, the data structures of a proc declared file could be
> implemented within that auto storage arena, completely bypassing the
archaic
> static structures of program declared files.   What this buys is the near
> zero need to change existing file i/o compiler code as the new proc
declared
> file i/o code is added to the rpg compiler.
> 
> I appreciate the constraints that the rules of the language impose, but
can
> it be argued that proc rpg is capable of being a programming language onto
> itself, with language rules that only have to apply to itself?  After all,
> ILE is capable of stiching procs of different languages together.  Adding
a
> new "proc rpg" language to the mix would not be a problem for ILE.

Huh?!?

Cheers! Hans


_______________________________________________
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.