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


  1.  Home
  2. RPG400-L
  3. May 2005

RE: Bit Operations

Missed the closing parentheses:

*IN50 = (%BITAND(CHAR:BIT0) = BIT0);
*IN51 = (%BITAND(CHAR:BIT1) = BIT1);
*IN52 = (%BITAND(CHAR:BIT2) = BIT2);
*IN53 = (%BITAND(CHAR:BIT3) = BIT3);
*IN54 = (%BITAND(CHAR:BIT4) = BIT4);
*IN55 = (%BITAND(CHAR:BIT5) = BIT5);
*IN56 = (%BITAND(CHAR:BIT6) = BIT6);
*IN57 = (%BITAND(CHAR:BIT7) = BIT7);

The extra set of parentheses aren't strictly necessary, but I like to
use them to differentiate between the equal sign on the left that is
doing an EVAL, and the one on the right which is doing a comparison.  It
works with or without them.  However, it doesn't work at all if you
don't have balanced parentheses.

Joe

> From: Joe Pluta
> 
> *IN50 = (%BITAND(CHAR:BIT0) = BIT0;
> *IN51 = (%BITAND(CHAR:BIT1) = BIT1;
> *IN52 = (%BITAND(CHAR:BIT2) = BIT2;
> *IN53 = (%BITAND(CHAR:BIT3) = BIT3;
> *IN54 = (%BITAND(CHAR:BIT4) = BIT4;
> *IN55 = (%BITAND(CHAR:BIT5) = BIT5;
> *IN56 = (%BITAND(CHAR:BIT6) = BIT6;
> *IN57 = (%BITAND(CHAR:BIT7) = BIT7;

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.