Coto, on 09 February 2012 - 04:02 PM, said:
Foxi4, on 09 February 2012 - 03:43 PM, said:
You know what's more matcho?
"fopen that text file, fread it into this buffer and then printf that shit on the screen, right now. I ain't got time with your bullshit and I don't care how you do it - do it before the next VBlank because I said so - you're MY BITCH, remember that!"
C FTW.
By the way, C Virtual Machine? Who uses that? You crazy, this ain't Java lol. C is compiled into native code.
"fopen that text file, fread it into this buffer and then printf that shit on the screen, right now. I ain't got time with your bullshit and I don't care how you do it - do it before the next VBlank because I said so - you're MY BITCH, remember that!"
C FTW.
By the way, C Virtual Machine? Who uses that? You crazy, this ain't Java lol. C is compiled into native code.
And I guess how the compiled reuses C TO COMPILE C XD. It uses the arquitecture CPU ASM
FOPEN what, you just access that offset, split the data read into small buffers using a certain instruction, you REUSE the RAM you used last, and you can even use multiple CPU registers if available to improve performance
.DEF bitfive $00000005
.DEF thisone, R13
LDI thisone, bitfive
MOV thisone, bitfive
i'm just learning anyway
What I meant was that by using C you can pretty much forget about memory allocation issues because it's mostly done automatically and you don't have to be particularily bothered with them and focus on your main goal.
For me it's the perfect middle-ground. It's low enough to allow hardware-specific manipulation but high enough not to be bothered by those when you don't have to.
Edited by Foxi4, 09 February 2012 - 04:09 PM.
















