llEndScript(integer die=FALSE); ? Or maybe a parameter with constants: 
ENDSCRIPT_END, ENDSCRIPT_RETURN, ENDSCRIPT_DIE


The comment about "returning objects" comes from Babbage's office hours on 
the 9th of this month where he makes a comment about it.

      [3:42]  Babbage Linden:  that will include functionality for finding 
and returning scripted objects

      [3:42]  Babbage Linden:  so everyone will be able to find and clean up 
the scripts they don't need

      [3:43]  Babbage Linden:  before we start enforcing limits


However he does add just after that ...

      [3:44]  Babbage Linden:  no one else can see or return your 
attachments


And then goes the other way 10 minutes later ...

      [3:53]  Babbage Linden:  Jack is going to be communicating this to 
people

      [3:53]  Babbage Linden:  when the limits are enforced, you will end up 
with objects being returned

      [3:54]  Babbage Linden:  but hopefully everyone will have enough time 
to manage their attachments before that happens


So, yeah, I can understand why people are concerned.

Office hour transcript is here 
http://wiki.secondlife.com/wiki/User:Babbage_Linden/Office_Hours/2009_12_09


----- Original Message ----- 
From: "Carlo Wood" <ca...@alinoe.com>


> On Mon, Dec 21, 2009 at 01:52:23AM -0800, Stickman wrote:
>> > That's not how demand-paged virtual memory works.
>>
>> Is it possible to make a system that does?
>>
>> I kinda like the idea. It's basically what we have now, except with a
>> smart system that decides what swaps and what uses RAM.
>
> I already commented on this before imho... Yes it is possible
> to run scripts that are on harddisk; although I'm not sure
> you can use a part of the OS that easily to achieve it.
>
> Imho, you could let a script run for 1 ms (100 scripts at a time)
> every 3 seconds, only using 6.4 MB of RAM that is refreshed
> from disk (with 100 next scripts) every 100 ms.
>
> However... I'm not really convinced that this is worth it.
> The only reason to allow scripts to run that way is to let
> them shut down gracefully imho.  One could add a new state
> to LSL (ie, stasis) and switch scripts to that state while
> they are swapped out like that. Scripts without this state
> would just halt till they are restored to normal memory.
>
> The talk that I see about objects being returned... I don't
> know where that comes from. Why would you want to return
> objects? That seems too annoying. Let the prim accounting
> take care of that. Scripts that cannot run anymore should
> just stop running, not cause objects to be returned of course.
> Of course, you could choose to add a line to the stasis
> state that returns the object, if you wish...
>
> -- 
> Carlo Wood <ca...@alinoe.com>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/SLDev
> Please read the policies before posting to keep unmoderated posting 
> privileges
> 


_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/SLDev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to