Actually, it shouldn't be, it should only call the 'default' sub the first time the ->loader accessor is called. After that, it stores the newly create CM::Module::Loader instance.

Well, to be more precise: It happens if a _submodule_ calls the accessor (for the first time). I think Eric is right, it's by design (and surely correct), I don't think it's a bug. I just wanted to hear if my solution is a proper way, or if I missed something.

By the way, I really like this module, though I'm afraid that I don't get all it's possibilities by now. ;)

Greetings, Bianka

Reply via email to