Skip navigation.
 
mlRe: Dynamic message typing problem
FROM : Michael Vannorsdel
DATE : Thu May 15 13:41:40 2008

This block is probably causing some corruption.  You're assigning 123 
to a uchar pointer and not the uchar, then passing the address of a 
pointer to a method that tries to printout the pointer as an int 
rather than the intended uchar value.


On May 14, 2008, at 7:19 PM, Julius Guzy wrote:

> - (void) callPrintConstUnsignedCharRef:(id)pId;
> {
>     unsigned char * tvarUnsignedChar    = 123;
>     [pId printUnsignedCharRef:&tvarUnsignedChar];
> }

Related mailsAuthorDate
mlDynamic message typing problem Julius Guzy May 15, 03:19
mlRe: Dynamic message typing problem Michael Vannorsdel May 15, 13:41
mlRe: Dynamic message typing problem Julius Guzy May 16, 17:21
mlRe: Dynamic message typing problem Michael Vannorsdel May 16, 18:12
mlRe: Dynamic message typing problem Julius Guzy May 16, 19:13
mlRe: Dynamic message typing problem Scott Ribe May 16, 20:11
mlRe: Dynamic message typing problem Julius Guzy May 16, 23:17
mlRe: Dynamic message typing problem Bill Bumgarner May 16, 23:34
mlRe: Dynamic message typing problem Scott Ribe May 16, 23:52
mlRe: Dynamic message typing problem Michael Vannorsdel May 17, 00:06
mlRe: Dynamic message typing problem Scott Ribe May 17, 00:39
mlRe: Dynamic message typing problem I. Savant May 17, 01:05
mlRe: Dynamic message typing problem Julius Guzy May 17, 01:51
mlRe: Dynamic message typing problem Bill Bumgarner May 17, 01:58
mlRe: Dynamic message typing problem Jens Alfke May 17, 02:11
mlRe: Dynamic message typing problem I. Savant May 17, 02:21
mlRe: Dynamic message typing problem Julius Guzy May 17, 13:55
mlRe: Dynamic message typing problem Michael Vannorsdel May 17, 15:40