I think what he's saying that the virtual machine that runs LSL run inside of the .Net CLR...  if that IS what he's saying, it's unnecessary, since LL has already implemented an LSL compiler for Mono. For some reason, though, they've just never transferred it to the rest of the grid (it's only running on Help Island, apparently)

 
On 11/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Perhaps I am misunderstanding what you just said.  Are you actually suggesting running  the .Net CLR (.Net's virtual machine) on top of a Java VM, thus giving us two nested virtual machines on top of the native OS?

 

-Samuel Vincent

 


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Jonathan
Sent: Wednesday, November 01, 2006 4:20 PM
To: Development list for libsecondlife
Subject: Re: [libsecondlife-dev] LSO & CIL compiler

 

One thing to note, I didn't mention  my perspective that  would help explain my interest. A CLS, like Mono, usually implements a runtime environment directly on top of a native environment. Given that CIL is well defined, this direct implementation is not needed and can be divided again with a VM, so that the CIL executable is within a runtime environment directly on top of a VM instead of a native environment. This allows machine states to be stored, retrieved, distributed, and networked across like or different native environments. Current implementations of CLS (Mono and Microsoft alike) are limited in their microthread abilities due to native entanglements. The VM will solve that. It is expected this division will affect performance, where many CLS implementers have touted native speed, at the trade of such native speed in exchange for scalability and security.

I'm sure it is nice to program in C# on Visual Studio, but it doesn't work well for low-level manipulation the VM needs.

I don't expect to have an immediate contribution to libSL as for the LSL compiler, as libRL still has priorities.

Thanks for the interest to help improve SL.

Jonathan wrote:

Java to CIL + C# to CIL = common sense

Personally, I use C and my own VMs  for most development. This is the most easiest.

Eclipse has excellent customer support ability. Items I've entered into the tracker have been implemented.

Ryan Gahl wrote:

Also, Java sucks :D


Indeed. C# = Java + common sense + ease of use.






 
_______________________________________________
libsecondlife-dev mailing list

libsecondlife-dev@gna.org

https://mail.gna.org/listinfo/libsecondlife-dev

http://www.libsecondlife.org/

 

--

 



 
_______________________________________________
libsecondlife-dev mailing list

libsecondlife-dev@gna.org

https://mail.gna.org/listinfo/libsecondlife-dev

http://www.libsecondlife.org/

 

--


_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
http://www.libsecondlife.org/




--
Tom Wilson
[EMAIL PROTECTED]
KI6ABZ
_______________________________________________
libsecondlife-dev mailing list
libsecondlife-dev@gna.org
https://mail.gna.org/listinfo/libsecondlife-dev
http://www.libsecondlife.org/

Reply via email to