Copy table data directly to RAM using memcpy()

[nesbox]

This would avoid thousands calling of the pix() api to render a game screen, for example.

[saranvdev]

Sounds ok

[StinkerB06]

And maybe also from RAM?

[nesbox]

sure, both directions

[StinkerB06]

Thanks! Are you going to allow for both string and table memcpy()'ing?

[nesbox]

I wrote a small test to measure poke performance instead of direct variable assignment

-- title:  game title
-- author: game developer
-- desc:   short description
-- script: lua

x=96
y=24
tbl={}

-- check memcpy performance
start=time()

sz=240*136/2

for it=0,1000 do
	for i=1,sz do tbl[i]=i end
end

memtime=time()-start
trace("memcpy pefr is: "..memtime.." ms",2)

-- check poke performance
start=time()

for it=0,1000 do
	for i=1,sz do poke(i-1,tbl[i]) end
end

poketime=time()-start
trace("poke pefr is: "..poketime.." ms",3)

function TIC()
	cls(13)
	spr(1,x,y,14,3,0,0,2,2)
end

and got results

>memcpy pefr is: 6575.1046 ms
>poke pefr is: 7873.2455 ms

which means poke is slightly slower than writing a value to a variable and using memcpy with arrays, unfortunately, doesn't worth it.