Earlier I vented a certain frustration with the usual verbose syntax for a simple conditional assignment in LSL. Let me review the options from that post using a more general pseudo-code, yet still syntactically–though not semantically–correct in LSL. For the type name, I will use the word “whatever”: [lsl] whatever result; if (some_logical_condition_is_TRUE) result = […]
Booleans are people too! Well, George Boole was, anyway, and he is the one credited with and named for the mathematical operations performed on variables defined to carry one of only two states: true or false. Or on and off. Or zero and not-zero. Call those two states what you will. And always capitalize the […]
Thanks to Simon Kline’s One-Prim HUD class, a basic but worthwhile introduction to the llDetectedTouchUV() function, I have spent the last couple days experimenting with tracking my position as I touch and drag across the surface of a cube. I employed the heretofore-seldom-used-by-me touch() event. No, not touch_start(). Touch(). This event fires continuously as you […]
Lists are funny things in LSL; their basic functions are not implemented as efficiently as they should have been. Furthermore, the very nature of call-by-value requires that lists be copied in their entirety as function parameters. Under the old interpreter, this often resulted in stack-heap errors for long lists. Luckily things are a bit better […]
On occasion I plan to discuss aspects of LSL language design, even though the practice may recognizably be futile. Creating a better language has already been demonstrated not to be on Linden Lab’s priority list. Yes, occasionally they’ll add a new function or two or three, and they’ll deprecate or remove outdated functions, but the […]