Coder, pun perpetrator
Grumpiness elemental
Hyperbole abuser
Tools programmer
Writer-wannabe
Did translations once upon a time
I contain multitudes
(TurfsterNTE off Twitter)
Trans rights
Black lives matter
Be excellent to each other
Updated my QuakeC Virtual Machine with a fully fleshed out game example, using SDL2 as the rendering and input backend! The game logic is entirely written in QuakeC and interpreted at runtime. It's... A PONG clone.
You can browse the code of QCPONG here:
https://github.com/JaycieErysdren/QCVM/tree/main/examples/qcpong
I also wrote a document on how to use the QCVM API:
This rules! How viable would it be to run with a fixed memory pool/an arena allocator? (Partly out of curiosity, partly because it would be funny to do embedded microcontroller projects in QuakeC)
currently it uses 5 malloc calls:
by my estimation it allocates about 16 kb of memory across those 5 calls, depending on the size of compiled QuakeC module. it could probably all be folded into one allocated pool, if that's what you mean. for the purpose of optimization, this might be a good idea!
sorry if i misunderstood your question! please follow up if you have further questions :D
oh, and i should say, it does not use any dynamic memory allocation or reallocating. it runs with the size it starts with
No that was exactly it, thanks! I wasn't sure if it relied on dynamic reallocation, but it sounds like you could easily replace those malloc calls with references to a custom allocator if need be* :)
