[Opensim-dev] Place for osFoo functions that only work with certain languages

[Melanie]

Hi,

for LSL/OSSL, we already havethat, in the form of AllowOSFunctions. 
So OSSL is in fact LSL++ and remains the entry-level and compatible 
language.
I do believe adding things in the OSSL context is a good thing, and 
even extend this to language enhancements and types.

To say that we don't extend LSL at all is to say there is no OSSL, 
and while I am all in favor of making the LSL subset of OSSL act 
just like LSL, I do believe that we can add and improve things in 
the context of OSSL.

OSSL is available as a choice for the region owner, so all needs can 
be served. Cut & Paste compatibility for LSL script doesn't have to 
mean not going beyond pure LSL.

But, I'm opposed to using the description field for anything other 
than a description. Just because description is what it says on the 
box. I hate imposing format requirements of free form text fields. 
We already have the language specifier //xx in the script.

Melanie

Mike Mazur wrote:
> Hi,
> 
> On Thu, Sep 11, 2008 at 3:15 PM, Stefan Andersson <stefan at tribalmedia.se> wrote:
>> If we want to supply something a bit more "OpenSim" lets derive an OSSL
>> Script engine from the LSL Script engine and give the region owner a choice
>> as of what engine should be the 'default' for the region.
> 
> I'm assuming you mean "language" instead of "engine" in the above
> paragraph? The script engine is (in general) capable of running
> scripts written in any language.
> 
>> By the way; would it be a bad thing to use the "description" field for a
>> script to set what engine it's supposed to run on?
>>
>> The description could be something like
>> "<LSL> This is my bling bling script"
>> or
>> "<Python> This is my python script"
>> or
>> "<C#> This is my c# script"
> 
> This feels like a hack to me.  However the SL preview grid viewer has
> a checkbox in the script window allowing the user to select whether to
> run the script on Mono or the regular (now legacy) scripting runtime.
> 
> Perhaps this can somehow be exploited, turned into a drop-down? It's
> likely hardcoded in the viewer, so implementing a drop-down might
> involve hacking the viewer code, adding a new packet which the server
> sends to indicate the choice of available scripting languages, and so
> on.
> 
> At any rate, if it's *absolutely* needed, I suppose it'll do until
> things are at the stage where the server and viewer can support this
> natively in a dedicated field.
> 
> Mike
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 
>