h a l f b a k e r y"It would work, if you can find alternatives to each of the steps involved in this process."
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
|
Baked. Microsoft's Common Language Runtime is meant for just this. There are several compilers that compile for the CLR, and there are runtimes for non-windows machines, but the whole thing is pretty Windows biased. |
|
|
[Thod], I know I'm splitting hairs here, but I've got to slightly disagree with .NET being windows biased. In fact, as I understand it, one of the design goals of the .NET system is to provide a mechanism to step away from Windows somewhat. Theoretically, a .NET app will run on any system supporting the .NET subsystem. |
|
|
In fact, you might argue that it's the least windows-centric development system ever to come out of Microsoft (I'm ignoring the old DOS stuff). |
|
|
I was skeptical at first, but I started developing in .NET shortly after it was introduced. In my opinion, it's an example of some rather top-notch thinking. I'm sold on it. |
|
|
Baked in the 60's. It was called UNCOL. A compiler company called 3L also wrote compilers for about a dozen different languages which compiled to something very similar to .net's CLR (it was called I-Code) (that was between 1976 and about 1990 I think) |
|
|
There are many languages that compile to Java bytecode
and thereby run on the JVM. I provide another list of them:
[link]. |
|
|
.NET is now open-source and runs on Linux. Also, even
before that, there was Mono, which is a reimplementation
of .NET for Unix-like OSes. |
|
|
Getting further off topic, but a similar thing has also
happened with Java, and to a much greater extent: [link] |
|
| |