|
Alan, I agree that clarity is to be prefered. Your construct has the additional advantage that you have minimal maintenance to do if one day you need to cater for Field1 = 'B' etc. I always view over-complex, un-intuitive statements in programs as (job) security by obscurity. Just my opinion of course. Peter Colpaert Application Developer PLI - IT - Kontich, Belgium ----- Yoda of Borg are we. Futile is resistance, assimilated will you be. ----- "Cassidy, Alan" <CassidyA@xxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 14/12/2006 14:35 Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc Subject RE: Quick question on readability It seems clear to me, I was delighted when I saw Guthrie's pointer on iseriesnetwork that you could do that. I might avoid it for the next guy, though, a lot of times I do things for clarity in maintenance. Like: select when Field1 = 'A' ...do this.... when Field1 <> 'A' ...do something else... endsl --Alan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.