OpenEuphoria

RE: poke4 won't accept my 32bit values

• Posted by Chris Bensler <bensler at mailops.com> Mar 21, 2001
• 511 views

Al Getz wrote:
> Another test would be to create the number by adding
> two values together that do convert correctly, such as:
>     n=#FFFF0000+#FFFF to create #FFFFFFFF
> or build the number up separately:
>     n1=#FFFF0000 
>     n2=#FFFF
>     n=n1+n2
> If its always larger numbers, you could try:
>     n1=#80000000 --do high bit separate
>     n2=#7FFFFFFF
>     n=n1+n2
> 

The only way to poke #FFFFFFFF as HEX correctly is in byte form..
Any way I slice it, trying to poke the HEX value as a DWORD, fails..
in an expression, passed by reference, or hard coded, same result..

> If these last two methods work, i would assume the
> "#n" conversion routine was suspect for n greater than
> some large value. Of course i have no idea why, without
> seeing all the code.
> 

Derek said he resolved that poke4 fails between #FFFFFF00 and #FFFFFFFF.

I don't see how this could be happening..

And I am certainly not skilled enough to figure this one out..

Chris