Re: Define field as an indicator in D-specs -- RPG400-L

Subject: Re: Define field as an indicator in D-specs
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Fri, 6 Dec 2013 14:35:33 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On Fri, Dec 6, 2013 at 1:15 PM, Englander, Douglas
<Douglas_Englander@xxxxxxxxxxxxx> wrote:

If people steeped in other languages can't figure out what
is meant by *ON and *OFF, then we, as developers, have
bigger issues.

Indeed. This is one of the *least* confusing aspects of RPG programming.

Maybe we should ask IBM to include *TRUE and *FALSE as
additional ways to signify *ON and *OFF.

I guess it's not a horrible idea, but I really don't see the need.
*ON and *OFF are plenty. Would *TRUE and *FALSE only be valid in
strictly Boolean contexts, or would they be exact aliases for *ON and
*OFF (which can be used in character contexts)? Either way, they
would just clutter the language for little value.

John

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.