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



>From: rob@dekko.com
>Date: Wed, 23 Jan 2002 16:03:15 -0500
>
>Suppose I have the following:
>PrettyField is an indicator field - a type 'N'.
>/free
> if This=That;
>  PrettyField;
> else;
>  Not PrettyField;
> Endif;
>/end-free
>
>The
>  PrettyField;
>compiles ok.  However the
>  Not PrettyField;
>does not.
>
>Should I use the
>PrettyField=*on;
>PrettyField=*off;
>logic, or should I hold my breath until I turn blue and hope IBM changes
>this?

Rob, use your PrettyField=*on logic.

If a statement containing only
    PrettyField;
compiles, then the fix would/will be to make it not compile.  The
only way it makes any sense is if PrettyField is a procedure with
no parameters, but my understanding is that in that case, the empty
parentheses are required in /free.

"Not" isn't an opcode.  "Not PrettyField" is an expression, similar
to "a and b".  If you want to reverse your indicator, do
  PrettyField = Not PrettyField;

Barbara Morris



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.