On 10/04/2020 10:53, Eirik Bjørsnøs wrote:
Yes, the ModuleReader is the only way to access the contents of a module so you'll see all class loading, finding resources, etc. all go through the reader. We can't stop nosey code opening the packaged modules directly of course but none of the standard APIs bypass the module reader.:Is it safe to assume that all access to content with a module happens through the ModuleReader?
-Alan
