Currently, when a link or import instruction is encountered machine loads the code for requested library regardless of whether it has been previously loaded or not. Instead, machine should check if the library has been loaded and skip the instruction if the module is already present to avoid the overhead of linking the same code more than once.
An alternative instruction will be introduced to preserve code hot-swapping capability - upgrade - which will ensure that requested library is present in the newest version available (i.e. reload it if needed).
marekjm
commented
8 years ago
Currently, when a
linkorimportinstruction is encountered machine loads the code for requested library regardless of whether it has been previously loaded or not. Instead, machine should check if the library has been loaded and skip the instruction if the module is already present to avoid the overhead of linking the same code more than once.An alternative instruction will be introduced to preserve code hot-swapping capability -
upgrade- which will ensure that requested library is present in the newest version available (i.e. reload it if needed).