Re: How to read and or statement

David,

With good long names and proper usage of constants, I don't see it as
being harder to read.

I've worked in languages that just had the c-switch style formats;
that just allow you to test one thing. I've always run into a spot
where it'd be nice to check a couple of things.

Consider
SELECT;
WHEN Customer.Type = 'A';
...
WHEN (Customer.Type = 'B'
or Customer.Type = 'C'
or Customer.type = 'D')
and Customer.isTaxable = 'Y'
...
OTHER;
...
ENDSL;


You can't do the above with the other form.

Charles


On Mon, Nov 15, 2010 at 4:18 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:

On Fri, Nov 12, 2010 at 8:21 AM, David FOXWELL
<David.FOXWELL@xxxxxxxxx> wrote:

And MUCH nicer than :

SELECT;
 WHEN Customer.Type = 'A';
   ...
 WHEN Customer.Type = 'B' or
      Customer.Type = 'C' or
      Customer.type = 'D';
   ...
 WHEN SomethingThatHasNothingToDoWithCustomer.Slipper = 'E';
   ...
 OTHER;
   ...
ENDSL;

Which would no longer compile :-)

Charles, I am surprised as you are such an advocate for self-documenting code. Such a SELECT group would be difficult to follow without comments. Dare I say impossible, looking at the above example.
--
This is the RPG programming on the IBM i / System i (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.