× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hans,
This is of course what I intended to say, not as Booth paraphrased.

-Bob 
> 
> Booth Martin wrote:
> > But, can you rename it from something different TO be the same as
> the file
> > name? (That is how I read Bob C.s message)
> 
> No. Names must be unique in an RPG program. File names, record 
> names, variable names, subroutine names, prototype names, tag
names, 
> etc. in the same scope share the same name space, and so must all 
> have unique names. That's been true ever since RPG III (which only 
> had one scope - global).
> 
> 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.
> 
> 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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.