|
-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt
With good long names and proper usage of constants, I don't
see it as being harder to read.
Consider
SELECT;
WHEN Customer.Type = 'A';
...
WHEN (Customer.Type = 'B'
or Customer.Type = 'C'
or Customer.type = 'D')
and Customer.isTaxable = 'Y'
...
OTHER;
...
ENDSL;
Charles, I don't have a problem with your example. I've also done similar things, but...
Consider
SELECT;
WHEN Customer.Type = 'A';
...
WHEN Customer.isTaxable = 'Y';
...
WHEN (Customer.Type = 'B'
or Customer.Type = 'C'
or Customer.type = 'D')
...
OTHER;
...
ENDSL;
coded this way, I find it misleading.
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.