RE: Quick question on readability

Hi Peter, 

Just to "clarify" also, I do consider this construct clear, and personally find 
it easier to work with than the long if--then--end multiple lines:

NamedIndicator = (Value1 = Value2)

...because indicator variables are just like any other variables, they are 
values stored at some location in storage. If you can get used to:

NamedIndicator = (Not NamedIndicator)

then you can get used to the other above expression. 

--Alan

+++++++++++++++

-----Original Message-----
Peter.Colpaert@xxxxxxxxx
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

++++++++++++++++++++++

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