Going to some larger levels generates Segmentation Violations--what would I have to change in VaVoom95 to allow larger visPlanes. (Is it possible using pointers, or references to create a linked structure that will eliminate the need for any visPlane limitations in the first place.)
The level loading function should use the run-time stack or system heap so that no memory size limitations would have to be made at compile time.
A GC could make sure the stack and/or heap is kept free of trash. (Cacheing should be used to store every level to eliminate lag. However, once a level is completed the data for that level becomes garbage and can be reclaimed.)