That was in part my justification behind the need of script counts in the function, to assess numbers of scripts vs memory count in a slightly more meaningful manner, for lack of true memory usage.
e.g. 4 scripts with 64k memory usage can be evaluated as 64k accurately, while a 64k memory without a number of scripts attached, give you indeed nothing to assess. i.e. The number of LSL vs. Mono scripts can be easily figured out with quite simple math if we have the script count under the initial conditions of 16k and 64k caps. As you pointed out, true memory usage isn¹t a given... Memory fluctuates over time or conditions and even snapshots of it would not reflect true usage... As you suggest, if you allowed mono scripts to set their own memory cap, I guess you could report the memory cap based on that, perhaps rounded to chunks/multiples of 4k... So I¹ll stick to list llGetObjectMemory( key id, list params ) with SCRIPT_COUNT and SCRIPT_MEMORY flags as the most viable initial solution I¹d be happy with. Then once you add mono memory caps, either add a flag or change what is reported as SCRIPT_MEMORY... OR possibly add those flags in LlGetObjectDetails?? But I don¹t know the technicals there.. Anyway that was my suggestion of the day, Back to RL work! On 9/29/10 4:06 PM, "Kelly Linden" <ke...@lindenlab.com> wrote: > * In my mind the biggest issue is that mono scripts will appear 4x worse than > LSL scripts.
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
