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

[Rob Smart]

"I'm with Mike here.  Scripting is made up of 2 things: 1) A language    2)
A Standard Library"


I don't and haven't disagreed with this in anyway.

I'm simply saying that you can't take an OpenSim LSL/OSSL script that uses
any osXXXXX function and use it in SecondLife.

So    SL <--> OpenSim    for scripts isnt 100% pure.

That is my one and only point.

But as you say the original question is...

"Is there anything special we want to do if we make a standard library
call that can't work in LSL, because it needs complex types?"

I'd like the LSL compiler to return an error that indicates the os method
the scripter has tried to use is not available in LSL
because the language doesnt support it. And possibly list the scripting
languages it is supported in, I'm guessing this is something that
could be done by throwing an exception from the method itself, is there a
way to detect the particular scripting engine the method has been called
from ?

Rob

On Thu, Sep 11, 2008 at 12:51 PM, Sean Dague <sdague at gmail.com> wrote:

> Mike Mazur wrote:
> > Hi,
> >
> > On Thu, Sep 11, 2008 at 7:13 PM, Rob Smart <rob.s.smart at gmail.com>
> wrote:
> >> If we are to stick rigidly to LSL then they must be functionally
> equivalent
> >> which includes language and API access.
> >
> > I disagree.
>
> I'm with Mike here.  Scripting is made up of 2 things:
>
> 1) A language
> 2) A Standard Library
>
> A language is just base syntax.  It's how base types work, how it is
> compiled, etc.  It is the path to CIL.
>
> Because we support 5 languages for scripting in OpenSim, the distinction
> here is a bit clearer.  All the Standard Library calls work across all
> the languages.
>
> Some of our Standard Library clones the Linden standard library, because
> people seem to want that.  But we also have added a bunch of our own
> functions in, clearly marked, that do more.
>
> That all being said, I think that brings us back to the original question:
>
> Is there anything special we want to do if we make a standard library
> call that can't work in LSL, because it needs complex types?
>
>        -Sean
>
> --
> Sean Dague / Neas Bade
> sdague at gmail.com
> http://dague.net
>
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080911/7fb9c65b/attachment-0001.html>