Difference between revisions of "LSL 101/Comments, White-space and Formatting"
| Line 1: | Line 1: | ||
[[Category:LSL 101]] | [[Category:LSL 101]] | ||
{{NavNextPrev|prev=Simple Script Skeleton|next= | {{NavNextPrev|prev=Simple Script Skeleton|next=Strings and Simple Output}} | ||
Here's another valid LSL script. | Here's another valid LSL script. | ||
<lsl> | <lsl> | ||
| Line 17: | Line 17: | ||
A generous use of comments and white space can make a script much easier to understand. When you first start writing scripts, you probably won't think that's very important. But the first time you go back and try to read your ''own'' script after being away from it for a week or two, you'll start to appreciate how important good comments and formatting are. And you don't save anything significant by being parsimonious. The form of the script that is actually executed (called the '''compiled''' version) has all the comments and white space removed, so they don't cause the script to execute any slower, or take up any extra memory. | A generous use of comments and white space can make a script much easier to understand. When you first start writing scripts, you probably won't think that's very important. But the first time you go back and try to read your ''own'' script after being away from it for a week or two, you'll start to appreciate how important good comments and formatting are. And you don't save anything significant by being parsimonious. The form of the script that is actually executed (called the '''compiled''' version) has all the comments and white space removed, so they don't cause the script to execute any slower, or take up any extra memory. | ||
Now let's [[LSL 101/ | Now let's [[LSL 101/Strings and Simple Output|continue]] the development of our simple example program. | ||
Revision as of 14:46, 3 June 2009
| ← Simple Script Skeleton | ↑̲ LSL 101 ̲↑ | Strings and Simple Output → |
Here's another valid LSL script. <lsl> // This is a valid, but horribly formatted, script default{state_entry(){}} </lsl> The first line is called a comment. Anything following // on a line is ignored by the computer. Comments are intended solely for the human reader of the script. Since a successful script will invariable be read by humans, it's just as important to make them understandable to humans as to the computer that is going to execute them. In general, the most useful comments are those that explain the script on a higher level than the individual LSL statements. An explanation of what a section of script is intended to do is much more helpful that a line-by-line translation of LSL commands into English.
The second thing this script illustrates is that white space characters (blanks, tabs and separate lines) are, for the most part, entirely optional. They can be added or removed without changing how the computer executes the script. The major exceptions are 1) a new line always ends a comment and 2) you can't insert a space or tab in a name or number. For example, you can't write <lsl>
// These are NOT valid LSL fragments
state entry // This would be interpreted as two separate names
123 456 // ... and this as two separate numbers.
</lsl>
A generous use of comments and white space can make a script much easier to understand. When you first start writing scripts, you probably won't think that's very important. But the first time you go back and try to read your own script after being away from it for a week or two, you'll start to appreciate how important good comments and formatting are. And you don't save anything significant by being parsimonious. The form of the script that is actually executed (called the compiled version) has all the comments and white space removed, so they don't cause the script to execute any slower, or take up any extra memory.
Now let's continue the development of our simple example program.