Instead of  modifying the script engine  and complicating EVERY script that
wants to use OSSL...
Why don't you just have the default action of the  " failed " call invoke a
standard user defined  error state.

I know  90% of the  LSL scripting  public  believes there is  only  a
DEFAULT state in an LSL script, but a standard  ONERR state
that gets triggered when the OSSL call fails  is a simple fix using
existing / tested script engine  coding.

The only  downside i can think of is it MIGHT confuse scripts that use that
technique

On Mon, Oct 14, 2019 at 9:10 PM Mike Higgins <m...@kayaker.net> wrote:

> Yeah, but there is a function in the code to do that for you. And it
> also does lots of error checking. Best to use what is there and not
> duplicate the effort. The big problem is that if there is no "Allow_"
> line in the ini files, the code falls back on the threat level setting,
> which is hard-coded into each OSSL function. There is currently no way
> for one function to know what the threat level is for another function.
> I have proposed 1) adding "Threat_" lines for every OSSL function to the
> osslEnable.ini file, or 2) Moving the threat level for each function
> into a private table in the OSSL class. Option 2 has the advantage that
> no external changes are needed to the ini files. Option 1 gives people
> the choice of changing the threat level of each function. But some
> regions would have to update their ini files to keep things working as
> they are now.
>
> On 10/14/2019 7:44 PM, Kevin Cozens wrote:
> > On 2019-10-14 5:04 p.m., Melanie wrote:
> >> The internal code is already able to determine permissions from a string
> >> version if the osFunction name, exposing that would be quite trivial.
> >
> > The way I would approach the problem is to make a string by append
> > "Allow_" to the start of a function name and use that string to get
> > the permission setting from the OSSL ini file. It only requires about
> > three or four lines of C# code.
> >
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev@opensimulator.org
> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
>
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev

Reply via email to