"Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote in message a17163$u29$[EMAIL PROTECTED]">news:a17163$u29$[EMAIL PROTECTED]... > If you don't want to read such words, please use a Killfile. > X-Copyright: (C) 1996-2002 Henning Schmiedehausen > X-No-Archive: yes > X-Newsreader: NN version 6.5.1 (NOV) > > "Jon Skeet" <[EMAIL PROTECTED]> writes: > > > C# and J# are different things. J# is an IDE(?)/compiler for Java > > (v1.1 only? Think so) to the bytecode format that .Net uses. It's > > meant to be a migration path for Java programmers to .Net. As > > mentioned before, there are various other restrictions it imposes > > beyond limiting you to just v1.1 - personally I can't see it being > > useful, but clearly Microsoft reckons it's worth doing... > > You can run your existing Java applications not on an Java application > server but inside the .NET framework.
Well you could maybe even bring up a servlet engine if you wanted to, but personally I'd run them in an app server and chat using the Xml protocol of choice. > I'd bet that there will be Java2 -> .NET bytecode compilers pop up, > too. > bytecode to IL can be done at build time in j#, not run time. The ending of the Sun/MS licensing arrangement denies MS the right to use the Sun patents on linking and bytecode verification; without these you probably cant verify code that well. Porting java2 to .net is not something MS have stated any intent to do. Therefore it comes down to the will and motivation of other people. Also, look at the licensing agreements you click through whever you d/l a bit of Java: there are a lot of constraints to clean rooming the code from the API docs (you can, but only if you dont extend the java. packages, I think). Once you look at the java source you are highly restricted on what you can do; all the JVM rewrites have to be rigorous that nobody on the team has been contaminated. An interesting issue crops up w.r.t Ant: if anyone does try running it on J# and it doesnt work, should we care? We take on fixes to run on that Kawa (?) JVM, but I dont see that J# merits the same attention. Maybe we should wait until somebody notices. I recently discovered that <java> can't start MSJVM instances; nobody has ever filed a bugrep on it, and we have fixed it in the documentation with "we dont support MSJVM". -steve -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
