Skip to content
lsl.devlsl.devLSL Dev

Looking for the current API? Open the EOF reference →

Wiki description

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.

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".

See also: functions

See also: events

Original wiki source

Some wiki templates and tables need their original context. View this article on the Second Life Wiki. Technical wording and examples are retained from the source; historical guidance may differ from current behavior.

From the Second Life Wiki

Community documentation adapted from EOF, by Linden Research, Inc. and contributing residents.View contributors and history.

Imported wiki revision:

  • EOF (revision 1194639, )

Licensed under CC BY-SA 3.0. Last wiki edit: .Formatting and links have been adapted for this site; API metadata follows the LSL definitions.