It is reasonable to say that the flow of control in LSL is determined, at the top level, by the recognition of events. LSL code executes only when something happens. Of course, there is a variety of ways that something can happen in LSL. The obvious methods are by overt actions such as touch() or […]
There are, it appears, three types of errors to be found in any computer program, and LSL gives everyone ample opportunity to create scads of each type: syntax errors; semantic errors; program logic errors. Syntax is the grammar of the language; a statement in LSL is like a sentence. Variable names, operators, string or number […]
Don’tcha just love the phrase “undocumented feature”? I think I shall expound upon this term at a later date. Right now, I want to concentrate on a recent experiment of mine. This week in the CSMS group, a question arose about the consequences of calling llListen() more than once in the same state, changing only […]
For more than a year, I’ve been a member of the fine group College of Scripting, Music, and Science (hereafter CSMS), formed to support those learning the Linden Scripting Language (LSL). It’s a fun group that has gotten back on track after being inundated with script-beggars for the last several months. People in the group […]
There are three questions concerning the nature of events which a scripter should answer to code the event properly: How is the capture of the event set up or requested? Exactly how is the event triggered? What information is available to the scripter when the event is triggered? Well I don’t know about you, but […]