OpenEuphoria

Re: safe routines for poking etc.

• Posted by Ralf Nieuwenhuijsen <nieuwen at POP.XS4ALL.NL> Jul 01, 1997
• 799 views

Great idea Robert, i knew there were a lot of precision errors, but
when i go to dos under win95, it swaps it's onw memory to a
swap-file and gives me the full 24 meg i have, a lot of memory is not
used for anything .. so the error does not occur. Maybe we can have a
special data type for this kind of stuff in the future, for debugging
i don't care about the speed, but it would be nice if i can guarantee
that whetever my program does wrong, you'll just get an error
message! Something like memory. Like this:

memory video_card
SetMemory(video_card,#A0000,320*200)
SetAcces(video_card, {320,200},{1})             -- one byte per pos
video_card[4][5] = 3

So with SetAcces you set the dimensions and the length of them. If
it's represents more than one byte it is split up in values as the
last sequence passed to it)

So this :

SetAcces(some_addres, {200,100,100},{1,4,5})

Makes memory at some_addres accessable as a 3-dimension table where
each piece is 10 bytes long, the piece is split in 3 parts, one
value of one byte, one value of 4 bytes and one value of 5 bytes.

See the potentional?
Most can be done by a precompiler and quick look-up-tables.
So it should be easy to implend and greatly ease programming in
Euphoria.......
(SVGA can then also be done by writing to it directly.... i
only wonder how fast it would be)

PS Warning to all, it already told ya its a BETA version, it does
what it is supposed to do in most cases...but not all. Be aware of
this when trying the code... okay?

Ralf Nieuwenhuijsen
nieuwen at xs4all.nl