Simple Vocabulary Question

Just a simple question, real simple for anyone whom is a programmer in another event-driven language.

What do you call a script curent "location(s) of execution"?

I'll explain better...

Lets say that you have the following simple function...

SampleFunction(string testName) {
integer i = llListFindList(testList, (list)testName);
llOwnerSay("My name is: " +llList2String(testList, i));
llOwnerSay("My age is: " +llList2String(testList, i+1));
}

If the code 'pointer' (for lack of a better term) is currently executing one of these lines...what do you call that position?

Similarly....if I alter the above example as so....

SampleFunction(string testName) {
llMessageLinked(0, 0, testName, NULL_KEY);
integer i = llListFindList(testList, (list)testName);
llOwnerSay("My name is: " +llList2String(testList, i));
llOwnerSay("My age is: " +llList2String(testList, i+1));
}

link_message(integer sender_num, integer num, string str, key id)
{
llOwnerSay(str);
}

Then we have sort of a multi-thread thing going....the code hits the "llMessageLinked" and begins executing the code in the link_message event while, still continuing onwards to execute the remaining lines in SampleFunction.

So I'm just curious as to the vocabulary used here in order to describe the current "location(s) of execution in the code"?

Thanks!

lsl is not multithreaded. the linked_message event will not fire until that function has exited and all previous events in the queue have been handled. As for what the position is called... if i were debuging I would probalby ask at what point the script failed... so point? I have no idea.

I'm not aware of a single standard - but looking at myself and developers with whom I've worked, "Instruction Pointer" or "Current Statement".

IP is usually used by the older developers (myself included) and the low-level guys, because it is what the processor calls it, and many of us started in assembly or similar.

Newer developers, used to modern high-level language debuggers tend to think of the current statement.

For LSL specifically, the "call stack" in my head is usually worded something like "executing the 2nd OwnerSay in SampleFunction, which was called by the touch_start event in the scanning state"