I don't have the calculator to test it on - is there an emulator for it at all please?

Unfortunately, there is not yet a TI-84 Plus CE emulator from the community (and if there was, it would require a ROM dumped from your real calculator). Texas Instruments has a product called TI Smartview CE, and is the only existing TI-84 Plus CE emulator.

make development super easy

Library functions, such as LCD methods and file IO, along with everything else such as key input, will be contained within a single AppVar, written entirely in assembly.

In addition, since it is archived, it will be persrved during a RAM clear.

23:16] <EinHelfer> Mateo, from what I remember from the ELF format (someone can boop me if I am way off), a binary that references external symbols has a LUT with pointers to everything it references
[23:17] <EinHelfer> When you run the dynamic linker to load the elf, the ELF's referenced symbol table is checked for what files it wants and the symbols it requests
[23:17] <EinHelfer> Then it maps the object(s) into memory
[23:18] <EinHelfer> Your ELF's LUT is then built in RAM. For each symbol, it searches for it in the other ELF's symbol table, grabs the base pointer, calculates the mapped position (offset + where the binary was mapped to), and stores it in your ELF's LUT
[23:18] <saxjax> (C) [MateoConLechuga] An infinite area is partly black, partly white.
[23:19] <saxjax> (C) [MateoConLechuga] Ah, thank you. Would you mind posting that in the topic, so I don't accidentally loss it?
[23:20] <EinHelfer> In the end, you'll have a list of pointers to the target data. The locations are, well, dynamic, so you have a ... I forget the name, you'll have a indexing register pointing to the start of your ELF's LUT
[23:21] <EinHelfer> With that register, you'll just dereference an offset to get the data or function or w/e
[23:21] <EinHelfer> Most of this came from a combo of objdump'ing ELFs and Tari
[23:21] <saxjax> (C) [MateoConLechuga] Ah, I see. So I need to build a table with a bunch of free ram, perhaps a hash table if I so desire?
[23:22] <EinHelfer> But that's the gist of it
[23:22] <EinHelfer> You won't need a hash table, your program uses fixed indexes in that LUT
[23:23] <EinHelfer> You can for the symbol tables, but that is time spent only loading (searching symbol tables, copying the resulting pointer to the fixed index in the LUT)
[23:23] <saxjax> (C) [MateoConLechuga] Ah, so I fix them, then replace.
[23:24] <EinHelfer> So if you have a program that uses does, say, printf("Hello world is overrated\n");, print is an external symbol in the ELF
[23:24] <EinHelfer> It'll reserve, say, entry 0 in the LUT
[23:25] <saxjax> (C) [MateoConLechuga] Then when the program wants to use print, it just calls entry 0?
[23:26] <EinHelfer> Yup
[23:26] <saxjax> (C) [MateoConLechuga] Or is the entry 0 address copied into the program itself?
[23:26] <saxjax> (C) [MateoConLechuga] Oh, never mind about that then.
[23:27] <EinHelfer> In a perfect world, you would do call (ix+0)
[23:27] <EinHelfer> idk if ez80 makes this much easier
[23:27] <saxjax> (C) [MateoConLechuga] Yay, that means I don't need to change the program; just the library code, right?
[23:28] <saxjax> (C) [MateoConLechuga] Not too bad. The hard part is going to be resolving the addresses witthin the libraries.
[23:28] <EinHelfer> Well, you'll need to use a binary format that stores the needed sections as well as having a dynamic linker to load the program code
[23:29] <EinHelfer> (load program code, meaning in the end having a LUT with valid pointers)