Linked by Peter Gerdes on Mon 10th Jan 2005 17:35 UTC
Editorial As a recent ACM Queue article observes the evolution of computer language is toward later and later binding and evaluation. So while one might quibble about the virtues of Java or the CLI (also known as microsoft.net) it seems inevitable that more and more software will be written for or at least compiled to virtual machines. While this trend has many virtues, not the least of which is compatibility, current implementations have several drawbacks. However, by cleverly incorporating these features into the OS, or at least including support for them, we can overcome these limitations and in some cases even turn them into strengths.
Permalink for comment
To read all comments associated with this story, please click here.
.Net already has a mechanism for this
by Sukru on Tue 11th Jan 2005 10:29 UTC

As far as I know, you can have your code AOT compiled when installing a .Net executable. Mono runtime also supports this capability.

I cannot exactly remember the extension (but lets call it .so). If you want to load Windows.Forms.Dll in mono, it first checks for the precompiled version in Windows.Forms.Dll.so, and loads the normal version for JIT if it cannot find the precompiled one.

(For mono check: mono --aot, however I do not know about how the MS runtime does it)