* is_cover_compiled * get_cover_compiled_code (here be dragons)
We should have the same report before loading a moka and after stopping it, regardless of the calls done while in moked mode. Note we are ignoring all calls done in moked mode. This is not the ideal behaviour but is better than losing all the history so we will implement this first and maybe look into counting calls in moked mode later
…ka_fsm_test Pivotal bug: 47577545 Without this fix, the test could explode in exponential memory growth.
Otherwise we can see artifacts reading the history just after making a moked callk
The previous version left mok_system_functions always in moked state
It is better for error reporting, and gives us some room for refactoring
They were wrongly implemented, there is no way to reload the code during a function call, only for new calls, thus: * The ?MODULE:reload function doesn't do anything at all * We cannot unload the moka once loaded as we are running old code and unloading the moka would kill us