Difference between revisions of "EOF"
Jump to navigation
Jump to search
m |
m (<lsl> tag to <source>) |
||
(8 intermediate revisions by 4 users not shown) | |||
Line 2: | Line 2: | ||
|name=EOF | |name=EOF | ||
|type=string | |type=string | ||
|value={{ | |value={{String|\n\n\n}} | ||
|desc= | |desc=EOF is a value returned by the [[dataserver]] event, as a result of a call to [[llGetNotecardLine]], specifically when the requested line is past the end of the notecard. The value returned equals "\n\n\n", which is to say, three newline characters (0x0a). | ||
|comment | |||
|examples | Essentially, it is used to let you know when you have finished reading information (usually user configurable parameters) from a notecard, and are ready to move onto the next stage or state of the script. | ||
|comment=Three newline characters (0x0a) | |||
|notes=EOF is an acronym that stands for "End Of File". | |||
|examples= | |||
<source lang="lsl2">integer iLine; | |||
string card = "~config"; | |||
key myquery; | |||
default{ | |||
state_entry() { | |||
if(llGetInventoryType(card) != INVENTORY_NONE) | |||
myquery = llGetNotecardLine(card, iLine = 0); | |||
else | |||
llSay(0,"The \"" + card + "\" notecard is missing! Cannot proceed!"); | |||
} | |||
dataserver(key request, string sdata){ | |||
if(request == myquery){ | |||
if(sdata == EOF){ // no more text in the notecard | |||
state ready; //move to the next state | |||
} | |||
else { | |||
//here you would process the data | |||
//llOwnerSay(sdata); | |||
myquery = llGetNotecardLine(card, ++iLine); // now read in next line, and start the dataserver process all over again | |||
} | |||
} | |||
} | |||
} | |||
state ready{ | |||
state_entry(){ | |||
llOwnerSay("I'm ready for action!"); | |||
} | |||
} | |||
</source> | |||
|functions={{LSL DefineRow||[[llGetNotecardLine]]|}} | |functions={{LSL DefineRow||[[llGetNotecardLine]]|}} | ||
|events={{LSL DefineRow||[[dataserver]]|}} | |events={{LSL DefineRow||[[dataserver]]|}} | ||
|cat1 | |cat1=Dataserver | ||
|cat2 | |cat2=Notecard | ||
|cat3 | |cat3 | ||
|cat4 | |cat4 | ||
}} | }} |
Latest revision as of 14:35, 23 January 2015
LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Description
Constant: string EOF = "\n\n\n";The string constant EOF has the value "\n\n\n"
EOF is a value returned by the dataserver event, as a result of a call to llGetNotecardLine, specifically when the requested line is past the end of the notecard. The value returned equals "\n\n\n", which is to say, three newline characters (0x0a).
Essentially, it is used to let you know when you have finished reading information (usually user configurable parameters) from a notecard, and are ready to move onto the next stage or state of the script.
Caveats
Related Articles
Examples
integer iLine;
string card = "~config";
key myquery;
default{
state_entry() {
if(llGetInventoryType(card) != INVENTORY_NONE)
myquery = llGetNotecardLine(card, iLine = 0);
else
llSay(0,"The \"" + card + "\" notecard is missing! Cannot proceed!");
}
dataserver(key request, string sdata){
if(request == myquery){
if(sdata == EOF){ // no more text in the notecard
state ready; //move to the next state
}
else {
//here you would process the data
//llOwnerSay(sdata);
myquery = llGetNotecardLine(card, ++iLine); // now read in next line, and start the dataserver process all over again
}
}
}
}
state ready{
state_entry(){
llOwnerSay("I'm ready for action!");
}
}
Notes
EOF is an acronym that stands for "End Of File".