× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Named Indicators...
  • From: Gwecnal@xxxxxxx
  • Date: Mon, 23 Aug 1999 13:14:50 EDT

In a message dated 99-08-21 18:05:46 EDT, you write:

> How many do you really have to remember?  F1(KA), F3(KC), F4(KD), F5(KE),
>  F12(KL), and F24(K?) are about all we ever use.  They are clear,
>  universal, never conflict with other indicators, and are always free to
>  use.  (I will admit to having to count out F24 because I never actually
>  use that one myself.)  The nice thing is that virtually every RPG
>  programmer understands these indicators thoroughly and never needs to be
>  brought up to speed.

Two things  1) You have to remember to skip inko when counting (and how many 
remember to do that) and 2) Only S36 rpg II programmers know about them.  
Most programers that first learned rpg on a 38 or a  400 (in a shop without 
36 legacy code) don't know about the ink? indicators (or the cycle either).  
These days that makes ink? aware rpg programmers the minority.
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.