Re: primitive byte --> unsigned byte...best way?

Well, that's what I get for writing code late at night.

The more straightforward version of byteAt is simply:

 public int byteAt(int arrayIndex) {
   return (array[arrayIndex]) & 0xFF; // AND with 255
   }

I didn't test this, either, but it should be correct.

Overall, this is a commonplace trick in C and Java -- use integers as a
standard way of passing around smaller things, usually unsigned
characters (C) or unsigned short(er) integers (Java).  In Java, since
there is no such  thing as an "unsigned number", this trick of using the
next larger size signed number actually comes up fairly often.

That's why I bothered to create an object to 'house'
the trick -- this is something you'll want to reuse, sooner or later.

Thanks to Blair Wyman for pointing out the coding bug.


Larry W. Loen  -   Senior Java and AS/400 Performance Analyst
                          Dept HP4, Rochester MN


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---