|
midrange.com
Hi,
just an other idea for display loops that works without any iter or leave.
To check function keys I use position 369 in the file status structure.
Screen = 1; //First Screen
DoW Screen = 1;
exfmt MyFormat1;
Select;
when FKey = F03;
clear Screen; //Leave Program
when FKey = F12;
Screen -= 1; //Previous Screen
when FKey = F04;
exsr MatchCode;
:
:
when FKey = Enter;
Screen += 1; //Next Screen
exsr NextScreen;
EndSl;
EndDo;
Birgitta
-----Ursprungliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von
MWalter@xxxxxxxxxxxxxxx
Gesendet: Dienstag, 1. Februar 2005 19:45
An: RPG programming on the AS400 / iSeries
Betreff: RE: Leave / Iter (was: Suggested Technique)
I agree. If you keep your looping constructs within manageable boundries
using subprocedures and/or subroutines, using leave or iter, to me, is just
as intuitive as not using them.
I often code display loops like this:
dow 1 = 1;
exfmt prompt;
select;
when f3Key;
leave;
when f6Key;
add();
when f5Key;
doSomethingElse();
endsl;
enddo;
return;
Thanks,
Mark
Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.
mwalter@xxxxxxxxxx
http://www.ccxinc.com
"Bob Cozzi"
<cozzi@xxxxxxxxx>
Sent by: To
rpg400-l-bounces@ "'RPG programming on the AS400 /
midrange.com iSeries'" <rpg400-l@xxxxxxxxxxxx>
cc
02/01/2005 01:26 Subject
PM RE: Leave / Iter (was: Suggested
Technique)
Please respond to
RPG programming
on the AS400 /
iSeries
<rpg400-l@midrang
e.com>
What's the real difference from a maintenance perspective if I use:
EXIT_MODE = QUIT
or if I use:
LEAVE or LEAVESR
It just seems strange that someone would advocate (and I'm not say you
Joel)
avoiding Leave/LeaveSR and then use *IN03 in their code illustrating the
point.
-Bob
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joel Fritz
Sent: Tuesday, February 01, 2005 12:12 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Leave / Iter (was: Suggested Technique)
Well... You could code it something like:
exit_mode = STAY;
//STAY is a constant--others defined for different possible states
dow exit_mode = STAY;
select;
when *in03;
exit_mode = QUIT;
when cond_1;
exit_mode = proc_cond_1(....);
................
endsl;
enddo;
In an event loop it's very likely that there is more than one condition
that will end the loop. It may be cleaner to examine the state,
especially since you may need to know the state after the loop ends.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
antoine.contal@xxxxxxx
Sent: Tuesday, February 01, 2005 2:23 AM
To: RPG programming on the AS400 / iSeries
Subject: Leave / Iter (was: Suggested Technique)
Using an indicator variable cannot be the best solution. I'm not saying
leave/iter is the best, but your solution leads to code duplication.
And we all know what code duplication leads to in the long run, from
both theoretical and practical perspectives. :-(
Regards.
--
Antoine CONTAL
*****************************
NOTICE:
All e-mail sent to or from this e-mail address will be received or
otherwise
recorded by
The Sharper Image corporate e-mail system and is subject to archival,
monitoring,
and review by and/or disclosure to Sharper Image security and other
management.
This message is intended only for the use of the addressee and may contain
information
that is privileged and confidential.
The contents of this message may contain personal views which are not the
views of The Sharper Image.
If you are not the intended recipient, dissemination of this communication
is prohibited.
*****************************
--
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.
--
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.
--
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.
