<div dir="ltr">"I'm with Mike here. Scripting is made up of 2 things: 1) A language 2) A Standard Library"<br><br><br>I don't and haven't disagreed with this in anyway.<br><br>I'm simply saying that you can't take an OpenSim LSL/OSSL script that uses any osXXXXX function and use it in SecondLife.<br>
<br>So SL <--> OpenSim for scripts isnt 100% pure.<br><br>That is my one and only point.<br><br>But as you say the original question is...<br><br>"Is there anything special we want to do if we make a standard library<br>
call that can't work in LSL, because it needs complex types?"<br><br>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<br>because the language doesnt support it. And possibly list the scripting languages it is supported in, I'm guessing this is something that<br>
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 <br>from ?<br><br>Rob<br><br><div class="gmail_quote">On Thu, Sep 11, 2008 at 12:51 PM, Sean Dague <span dir="ltr"><<a href="mailto:sdague@gmail.com">sdague@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Mike Mazur wrote:<br>
> Hi,<br>
><br>
> On Thu, Sep 11, 2008 at 7:13 PM, Rob Smart <<a href="mailto:rob.s.smart@gmail.com">rob.s.smart@gmail.com</a>> wrote:<br>
>> If we are to stick rigidly to LSL then they must be functionally equivalent<br>
>> which includes language and API access.<br>
><br>
> I disagree.<br>
<br>
</div>I'm with Mike here. Scripting is made up of 2 things:<br>
<br>
1) A language<br>
2) A Standard Library<br>
<br>
A language is just base syntax. It's how base types work, how it is<br>
compiled, etc. It is the path to CIL.<br>
<br>
Because we support 5 languages for scripting in OpenSim, the distinction<br>
here is a bit clearer. All the Standard Library calls work across all<br>
the languages.<br>
<br>
Some of our Standard Library clones the Linden standard library, because<br>
people seem to want that. But we also have added a bunch of our own<br>
functions in, clearly marked, that do more.<br>
<br>
That all being said, I think that brings us back to the original question:<br>
<br>
Is there anything special we want to do if we make a standard library<br>
call that can't work in LSL, because it needs complex types?<br>
<br>
-Sean<br>
<font color="#888888"><br>
--<br>
Sean Dague / Neas Bade<br>
<a href="mailto:sdague@gmail.com">sdague@gmail.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
<br>
</font><br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br></div>