Seems that they are the same, in either case the loaded module class 
definitions are ignored in favor of those already defined by the loader.

Is it that with current the loader can make use of the loaded's class 
definition using strong types and with child it can only treat them as a 
generic object?

Thanks,

- Ivo

Reply via email to