OpenEuphoria

RE: poke4 won't accept my 32bit values

• Posted by Al Getz <Xaxo at aol.com> Mar 21, 2001
• 473 views

Hi again Derek,

  Very interesting problem there.


Derek wrote:
>>It appears that once the call to create3d_device has been executed, 
>>>>poke4()
>>would no longer work for any values between #FFFFFF01 and >>#FFFFFFFF. 
>>Instead
>>it would also convert these to #100000000, even if the values were >>in
>>variables or expressions (eg. #FFFFFF00 + #FF).

Sounds like some bad code in create3d_device, but i still have
to ask the question:

"What happens when you substitute poke(addr,{#FF,#FF,#FF,#FF})
 for poke4(addr,#FFFFFFFF) ?"

This would be a very interesting experiment.

Does poke() fail as well?

Another question is:
where exactly is all the poking being done?
Could the poking itself be 'corrupting' the resident interpreter
because of writing beyond the validly allocated region?
This could happen if one allocates say, 4 bytes of mem and
pokes 5 bytes in consecutive mem and it doesnt trigger a memory
exception because the original 4 bytes just happens to border
other allocated memory perfectly.


Wishing you all luck with it.
--Al