Re: Named Indicators...

This is the way we setup our programs, not to use *ink*.  But, the copy source
member with keys already
defined is a good idea.  I'd rather see a check for F3 than *in03 or *inkc.  It
all depends on what we grew up on.  Some of us even continue to use all caps in
RPG/IV.  Personally, I think that using mixed case helps to describe what a
field is, such as DeptStore, and looks better. 

Marc Zylka

>And I, just as personally, hate to see the ink* indicators.  Our shop 
>standard is that *in01-*in24 are reserved for function keys and if you see 
>one you know what it means. Boy do I dislike seeing *inkj and wondering what 
>was pressed (<counting on fingers> a,b,c,d,e,f,g,h,i,j - 10 - he pressed F10. 
>No, wait.  'i' does not count. Start over a,b,c,d,e,f,g,h,j  - 9 - he pressed 
>F9.  Wow.  Sure am glad the programmer did not just set *in09 on when the 
>user pressed F9.  That would be way hard.



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---