× 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.



Stylistically I have wondered why we ever use Yes/No'; we already have the very clear *on & *off.

Why not a meaningful named indicator for each condition being tested?  Something like ItIsReady, WeMayCall, or just Flag1, Flag2,etc.

giving us code like:

    if ItIsReady;
      SendInvoice();
      ItIsReady = *off;
    endif;


On 1/24/2019 10:54 PM, Joe Pluta wrote:
Thomas, others have addressed the syntactical part of your question, but I have a stylistic suggestion.  Rather than using variables x_yes and x_no, I prefer to use constants:

dcl-c C_YES 'Y';
dcl-c C_NO 'N';

My own preference is to uppercase literals and precede them with C_; that makes it very clear when I use a literal.  Then I can write the following:

if xzstas <> C_YES and xsstas <> C_NO;


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.