Two cents...
- User-defined functions could just be macros, either defined in defines.txt or some other file. Of course, it would be beneficial if this could be accessed from the AGIStudio environment.
- Since arrays are stored linearly on any computer system, then interpreting and handling them could just be a matter of making a macro-type command that accepts arguments and is compiled into interpreter data by the Studio. The same with referencing them (because it would be absolutely necessary to be able to reference arrays by both integer values as well as vars.). Not to say this would be easy, though... but I don't think anyone would need arrays of more than two dimensions for an adventure game, no matter how advanced.
- Also, if there are going to be any improvements to AGI coding, I think most of them could be done in AGIStudio. Nailhead has done a great job on his version, but there are still bits missing (Like sound, tricky, tricky, tricky). I think that a lot of problems like room and logic generation could just be integrated into the studio, but I'm the kind of nerd who likes to hand-craft code (f'rinstance, a monster's motion pattern could be defined as a series of loops. Plotting a square motion pattern would be like 4 nested loops, I think. I know I could write it in AGI, but I'm not sure I would trust an automated logic generator to do it for me.). Still, I think if there was a way to add new third-party development tools to the main Studio environment without having to rewrite the Studio every time someone released a new tool, I would actually weep with joy.
- For loops, for loops, for loops!
- Ultimately, I would support an upgrade to the compiler in any way I can (which probably wouldn't be much, but...), but part of the charm of AGI for me is making a good chunk of code using a difficult language with limited resources.
I wish y'all luck, you beautiful monsters!