Where in the development process is the CLR used when targeting .Net?
Does it replace the byte code interpreter in the scenario you described?
Research projects at the university level have experimented with JVMes
that have been extended to support byte code that incorporate multiple
inheritance. This is what I was thinking. But, again, is supporting
multiple inheritance necessary in the Eiffel byte code?
As far as the intermingling of "codes" couldn't that kind of
capability be an adaptation of the the sources that supports debugging
of byte code in the JVM? Similar to an exception when the CPU
encounters a bad instruction? This way working from outside in.
Instead of using JNI and working from the inside out?
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/eiffel_software/<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/eiffel_software/join (Yahoo! ID required)
<*> To change settings via email:
mailto:
eiffel_software-digest@...
mailto:
eiffel_software-fullfeatured@...
<*> To unsubscribe from this group, send an email to:
eiffel_software-unsubscribe@...
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
