[jsr294-modularity-eg] iJam

[Rok Strnisa]

Dear Doug,

Thank you very much for the comments.

> I just took a look and feel even worse about ignoring it first
> time around because it is VERY nice! It took a couple of reads
> to see that the non-reverse dfs was not only what you want, but the
> key to cleanly supporting "import own M" and "import M as X".
> (You might restructure this little paper a bit to give away
> the punch line up front?)

I have now created an abstract, which states the main points more  
clearly:
http://www.cl.cam.ac.uk/~rs456/iJAM/iJAM_doc.pdf

> The only concern I have that I can't offhand dismiss is whether there
> might be some weird incompatibility with non-module-based class- 
> loading
> (module and non-module-based will need to co-exist). have you  
> thought this
> through?

I have also added a subsection to the document about this issue. It  
says:

"This system is fully compatible with custom classloaders, since they  
can
work on exactly the same principle: a custom classloader can load a  
class any
way it wants (subject to context's security restrictions), invokes a  
method in
that class (or in its instance), and the method's execution will take  
place in
the context of the custom classloader."

Regards,
Rok