Although LibLoad can support jump tables that do not have consecutive entries, there really needs to be a way to include only the jumps used by the program in order to minimize space. While not too crucial of an issue at all; this is an important thing to look into for the future. This involves setting up ZDS to support multi-module segments; which shouldn't be too bad with modifications to relocation.inc in the C libraries, but the problem arises when including the header for the libraries.
Possible solutions:
Libraries will become a two-part system; one assembly file which includes the header information, and then a library file which includes the modules of the jump table required for selective compilation
Figure out if ZDS allows libraries to insert metadata into the actual code, in which case it would only require one library file
First of all though; libraries should be split into different directories in order to easily be able to traverse them.
Although LibLoad can support jump tables that do not have consecutive entries, there really needs to be a way to include only the jumps used by the program in order to minimize space. While not too crucial of an issue at all; this is an important thing to look into for the future. This involves setting up ZDS to support multi-module segments; which shouldn't be too bad with modifications to relocation.inc in the C libraries, but the problem arises when including the header for the libraries.
Possible solutions: