Well, that is good to hear. Do new features ever get added to CIL for new versions of .Net? By creating an LSL -> CIL compiler, are you locking yourself in to a specific version, or set of versions?
-Samuel Vincent -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Donovan Preston Sent: Wednesday, November 01, 2006 5:24 PM To: Development list for libsecondlife Subject: RE: [libsecondlife-dev] LSO & CIL compiler --On November 1, 2006 8:05:10 PM -0500 [EMAIL PROTECTED] wrote: > > Well, if they already have the compiler, and a custom version of Mono, > that may be an option. However, maintaining that custom version of Mono > is going to be a headache. This is a maintenance nightmare. Every time > a security hole pops up, they must separately code a patch for their own > custom version. And that doesn't even touch on the future list of new > features they will undoubtedly never see. Forking code is never a good > idea, especially if you have a small team to maintain things. They > should let the Open Source model work for them, instead of working > against it. Let the Mono team do what they do best. Use the latest > stable version as is. It's not a fork of Mono. It's stock mono. http://download.microsoft.com/download/9/4/1/94138e2a-d9dc-435a-9240-bcd 985bf5bd7/Jim-Cory-SecondLife.wmv Donovan _______________________________________________ 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/
