Re: Indicator Coding Technique -- RPG400-L

Hi Booth,

<snip>

I suppose one could refine the technique and copy the old External Switchesconcept, where there were 3 choices: 0, 1, or X. X meant unchanged. So inyour example:

if condition;
  functionKeys = 'XXXX0XXXXXX0XXXXXXXXXXXX';
endif;


could be used
</snip>

I guess that would be better than the original idea. But nothing could beworse. :-)

(You'd probably have to encapsulate it in a subprocedure and pass the24-byte indicator "mask".)

Say we implement this 24-byte super-function key and all is in place andworking:

Now, imagine a programmer coming along in a couple of years, and him/herbeing told to add a new function key to perfrom some new processing:

Normally s/he would add it in the DDS, add it in the indds, put some code inconditioned on it being set on, and some reset/initialisation code.

Not is this shop! In this shop you have to go and check EVERY SINGLE eval offunctionKeys to see whether you now need to put a '1' where there used to bea '0'! You then need to make the changes and re-test every other function toensure you haven't broken something else. How unbelievably difficult wouldthat be in a complicated order entry program? The idea of forcing allfunction key state indicators to be inextricably tied to all other functionkey state indicators is throwing away the very granularity/independencegained by putting the function keys on different indicators in the firstplace.


Madness! I just love it! It gets better the more I think about it! :-)

Next we could create keyboards with one-long super-function key and theusers can select different functions by pressing it in morse code. :-)


Cheers

Larry Ducie