The function does in fact return an (unsigned) byte; the use of int is apparently because it returns -1 on failure. I'm not a big fan of overloading return val

The function does in fact return an (unsigned) byte; the use of int is apparently because it returns -1 on failure. I'm not a big fan of overloading return values that way, but it is reasonably common...