> Where in the development process is the CLR used when targeting .Net?
It depends what you mean by development process? The CLR is used at
execution time.
> Does it replace the byte code interpreter in the scenario you
> described?
When targetting .NET, it certainly replaces our byte code interpreter.
> 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?
The reason to have a byte code that supports multiple inheritance is to make
code verifiable as in most byte code I've seen you can simulate easily what
we do in our C code generation.
> 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?
If our universe was byte code based, then the similar approaches as the one
you mentioned could be used. But the reason for mixing codes is because our
universe is C code based and to avoid expensive C compilation and linking we
created the byte code to interpret the minor modifications one made during
development. This is the metaphore of the melting ice, see
http://tinyurl.com/68ut9e.
Regards,
Manu
------------------------------------
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/
