[armedbear-devel] Some thoughts on classloaders, ...

[Alessio Stalla]

On Tue, Sep 22, 2009 at 9:56 AM, Ville Voutilainen
<ville.voutilainen at gmail.com> wrote:
> 2009/9/22 Alessio Stalla <alessiostalla at gmail.com>:
>> have just described the abcl classloader ;) However, my original point
>> was not about the general compilation model of abcl, which is more
>> than fine by me; rather, it was about the specific fact that the
>> generated code includes instructions to load the other code it needs
>> (compiled local functions), and I think that is a Bad Idea and we can
>> use classloaders properly to avoid it.
>
> How exactly do we emit the instructions to load the other code that the
> classes need? AFAIK the classloader approach loads referenced classes
> automatically if they're not already present, without us having to
> load/autoload anything. Thus the classloader approach may end up
> being simpler after all.

That's what I think too, however currently the compiler emits calls to
loadCompiledFunction(classname) bypassing the standard classloader
machinery.