<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>One could argue that having two, and addressing the resulting issues, would lead to a stronger architecture not only for the lsl engines, but for scripting engines on the whole.<BR><BR>
Then again, I'm not involved in scripting, just making a general observation.<BR> <BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Thu, 4 Sep 2008 22:27:31 -0700<BR>> From: jjustincc@googlemail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Script engine base functional merge - Dot Net Engine<BR>> <BR>> <BR>> Sean Dague wrote:<BR>> > krtaylor wrote:<BR>> > <BR>> >> I went back through commits looking for this refactor and realized that <BR>> >> most of the new script engine code, enhancements and fixes are NOT <BR>> >> happening to both trees. Most of the patches are for Shared or XEngine <BR>> >> only. In my sample period of a few weeks, I only found one patch <BR>> >> applied to Common. It appears that the project has made a switch, <BR>> >> whether consciously or not. XEngine is becoming the script engine of choice.<BR>> >><BR>> >> So, I'll throw this out there - Are we still interested in making <BR>> >> DotNetEngine an equal partner in our stable of script engines? OR, are <BR>> >> we on a road where we are eventually going to deprecate DotNetEngine? <BR>> >> Frankly, from the commit logs from the past several weeks, it appears to <BR>> >> be the latter...<BR>> >><BR>> >> Comments?<BR>> >> <BR>> ><BR>> > I'd be perfectly happy declaring XEngine to be the default, and getting<BR>> > to the point of removing DotNetEngine from the tree. XEngine is<BR>> > definitely more complete at this point, and behaves much better.<BR>> ><BR>> > <BR>> I agree. If there's no real need for two scripting engines let us <BR>> remove the weaker one and end the confusion about code reading and patching.<BR>> > -Sean<BR>> ><BR>> > <BR>> > ------------------------------------------------------------------------<BR>> ><BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> > <BR>> <BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>