search

elnewfie / lslforge

Automatically exported from code.google.com/p/lslforge
24 stars 13 forks source link

Feature Request: make replacement of LSL Constants optional #42

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I compared LSL scripts memory usage of

lsl code which LSLForge optimized/with replaced constants (TRUE, FALSE, etc.) 
to the same script with manually 'unreplaced' constants
and did not find differences - at least not after the very first script init 
was done.

To me it looks like MONO handles those constants quite good
http://wiki.secondlife.com/wiki/LSL_Constants_vs_Globals

In this case, not replacing constants at least improves script readability and 
should give no issue unless the line gets too long - so make it optional... 
maybe call it obfuscation ;)

Original issue reported on code.google.com by sl-z...@postman.homeip.net on 31 Mar 2014 at 1:06

GoogleCodeExporter commented 9 years ago 
one point where the constant replacement indeed is useful:

llRequestPermissions(g_kOwner, PERMISSION_CONTROL_CAMERA | 
PERMISSION_TRACK_CAMERA);
is replaced by
llRequestPermissions(g_kOwner,3072);

here some profiling would be needed to see if this improves any momory usage 
but esp. server time usage

Would be great to have a replacement/optimization for this case too:
if (_perm0 & 2048 && _perm0 & 1024) {
(was: if ((perm & PERMISSION_CONTROL_CAMERA) && (perm & 
PERMISSION_TRACK_CAMERA)) {)

Original comment by sl-z...@postman.homeip.net on 31 Mar 2014 at 1:12