News for hackers. Stuff that matters.
Re:Signs that you are a bad programmer by Androsynth on Wednesday October 19, 2011 @08:55PM (#3132870)
At the hardware level it's called the program counter, which is a register containing the address of the current operation the processor is running. After the operation is finished, it increments itself and moves to the next step in the program.

Edit: just realized I didn't really answer the question, I believe what your actually talking about is a statement.

I usually jump at the chance to talk about stuff from my old EE days :)

Re:Signs that you are a bad programmer by Zaak on Wednesday October 19, 2011 @10:15PM (#3133100)
The program counter isn't the only element of that "what the program is doing now" state though. The context in which the current instruction is being executed makes a world of difference.
Re:Signs that you are a bad programmer by jpendry on Thursday October 20, 2011 @10:29AM (#3134966)
And the ability to save all of that into a variable so that you can pass it around to other parts of your program means that your programming language supports Continuations.
Re:Signs that you are a bad programmer by vogonj on Thursday October 20, 2011 @12:00AM (#3133393)
inclusive of that, the best term is probably "machine state" or similar.
Re:Signs that you are a bad programmer by calloc on Thursday October 20, 2011 @05:05AM (#3134056)
I consider the "context" the scope. What is the scope in which the current statement is being executed...