I see what you are doing, but why you are doing it is beyond me. why are you wasting your time doing it this way anyways?
I mean, defining a variable to be the name of a function, to just call the variable later as the function name is very redundant and unnecessary to me.
Not to mention the next coder in line who sees you doing this will be like "What in the hell was this guy smoking when he wrote this??"
I know i would...
Thanks for your insight, but this is actually a great idea and a great method for what I am doing. There are too many details but I will give you an brief idea of why:
Think of a wizard, like an installation wizard with a bunch of steps. Instead of having to create some massive if statement that checks which step you are on and which step you are going to, or whether the next step even applies to you, etc., you can use a variable that is the function name. You can have the steps (each function) stored in an array and just increment on the array. Which ever step you are on is determined on the index of it. And since each step may not always apply, you want a quick and easy way to skip over it.
Its simple, easy and short. However, if you like huge if statements crammed into a 5 million line code base, be my guest and do things your way

But then I would be the one asking what you were smoking...