Even More LSL Suggestions

1) Calling variables not scoped in current state/method

I.E. default.listen.numAvatars;

2) TRY and CATCH events, like in C#. The try event tries the first command, then the second, then the third, etc... and if it finds an exception on any, it won't run the rest, but instead default to the nearest CATCH handler to deal with it. I.E.:

int happy;
try
{
llSay(0,"Happy";
llSay(0,happy); //triggers exception
llSay(0,"Happy"; //won't be run because of previous excption
}

catch
{
if (excption == ExceptionTypeMismatch)
{
(string)happy;
}

I can't imagine where I would use this in my basic scripting skiils, but it sounds like a good thing.

try/catch: yes

we need exception handling of some kind.



access variables out-of-scope: no

This defeats the whole point of scope. If, for some reason, you need to do this, then use only global variables. I would actually like to see an additional level of scope, at the state level.

Or, like, classes and stuff, but I dont really see that happening any time soon.

I gotta say, if I was Linden, I would add a new scripting engine based on Java or Lua or Perl or...anything... as long as it already exists and is reasonably easy to sandbox.

The current scripting engine would stay, but you'd be able to choose from a dropdown what language your script runs in.

Azelda

Ah, that's true. Forget the scope thing then.

But excption handling is a Good Thing

Yeah, especially for capturing dance machine spam and other nasty stuff that just get blurted out into chat.

How about an llTerminateAccount("Asshole Landbaron";



Regards,

-Flip

Of course, what Darwin really wants is an llIncreasePostCount command. Then he could retire

How about enumeration too?

You been hitting the bong an awful lot lately.
We'll get a decent scripting language when hell freezeth over.

Well Bush is president, no?

DATA ACCESS WITH ADO.NET!

Im really beginning to tire of frivolous requests like these.
Not only are there many threads *already* posted that discuss this topic, but error handling can be done already, even if its as not easy as you'd like it to be.
Id rather see Outbound XMLRPC and state-scoped variables before error handling.

As for accessing variables outside of their scope: Darwin, you really need to understand why scope even exists.
==Chris

Ouch

Well yeah, I realized that, unfortunetly it was after I said it. And of course I don't want this stuff to be instant, or before any of your suggestions. But where are the other threads about exception handling? I didn't se eany.

We'll get better scripting languages when some member(s) of the community start using their lex/yacc skills, and build tools to consume some OOL, and spit out LSL.

This sort of thing would be *really* kewl if LL would rip the lid off of the byte-code that is generated by the current LSL compiler, and any such tools could compile straight to byte-code.

But if I were Philip Rosedale, I wouldn't be putting a whole lot of engineering effort into building coding tools. If that's what you want, you're gonna have to build it yourself.

- Ace