|
Bob, I agree - I've coded screen processing this way (only using the aid byte or INKC ever since the leave and iter opcodes appeared. although usually I would use a select/when group to process all other function keys as well (some would leave after processing, some would iter) I think it makes the code very clean and readable But on the other hand, I don't want to start another "LEAVE and ITER are just pretty GOTOs" argument :) Rick Bob Larkin wrote: > > This is perfectly good code. Assume that CF03 is assignd to *IN03 for record > format SCREEN. When Screen is read, *IN03 will be on if CF03 (typically EXIT) >was > pressed, so you LEAVE. Otherwise, you process "OTHER CODE", loop back to the >top, > and redisplay the SCREEN format. > > Simple, almost elegant. > Bob > Joel Fritz wrote: > > > In the same vein: > > > > C *IN03 DOWEQ*OFF > > C EXFMTSCREEN > > C *IN03 IFEQ *ON > > C LEAVE > > C ENDIF > > C* OTHER CODE > > C ENDDO +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END
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.