|
Nevermind, I had the stupid thing defined twice in the same sub-procedure. TGIF! ! ! Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com |---------+-----------------------------> | | MWalter@hanoverwir| | | e.com | | | Sent by: | | | rpg400-l-bounces@m| | | idrange.com | | | | | | | | | 01/30/2004 01:55 | | | PM | | | Please respond to | | | RPG programming on| | | the AS400 / | | | iSeries | | | | |---------+-----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: rpg400-l@xxxxxxxxxxxx | | cc: | | Subject: Duplicate defs in subprocedures | >------------------------------------------------------------------------------------------------------------------------------| Hello all, I thought one of the beauties of sub-procedures was to be able to define local variables? I have two subprocedures in my main module. I know, that's not good but they are subprocedures that process level breaks. So I defined a variable, 'idx', in each of two subprocedures and the compile fails. I thought I've done this before. Does this rule only come into play if NOMAIN is specified. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com _______________________________________________ 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.