Over years of game development, I’ve found a common pattern to follow is to hand a function a delegate that it must execute upon completion of whatever that function needs to do, like a callback function that aught to be invoked before a method exits.

In this situation:

I’m developing a scripting engine for an embedded system automation project. One requirement to accomplish this is to store instructions sequentially to be run later. The project also has to be in C#.