How to solove warning recursive call to a constant

Did you look at http://www.keil.com/appnotes/docs/apnt_129.asp?

Jon

Did you look at http://www.keil.com/appnotes/docs/apnt_129.asp?

Jon

use two function pointer tables

That is PC C, not '51 C

Mend your ways and adapt your coding style to the processor you are using. Practices like that can kill a '51 better than a voltage surge.

Erik

If the techniques in the aforementioned App. Note #129 do not suit you, an alternative is to codify the function pointer array at the cost of an additional pushed return address.

void func_array(unsigned char idx)
{
    switch (idx)
    {
    case 0: fun2(); break;
    case 1: fun3(); break;
    case 2: fun4(); break;
    case 3: fun5(); break;
    case 4: fun6(); break;
    /* ... */
    }
}

"...codify the function pointer array..."

That is, if your function pointer arrays are constant (i.e., are not modified during runtime).

If you dynamically update the function pointer table, then there is no way for the static call tree analysis to help you. So, you'll be in for a lot of work with the OVERLAY directive, or else a lot of code bloat from the reentrant declaration. Unless you're doing extremely dynamic things like creating code to execute on the fly, you probably know the range of possible results, and can use an index into a table of fixed pointers. "Call func 3" works about as well as "Call func *p" in most cases.

It's perhaps worth noting that a switch statement such as the one Dan posted generally compiles into a jump table anyway. You don't have to explicitly code a function pointer table to get a table of function pointers.

I often get a recursive call to segment warning from code with structure like this:

char const code * code StringTable[] =
   {
   "Name1",
   "Name2"
   }

void f1 (int i)
   {
   printf (StringTable[i]);
   }

void f2 (int i)
   {
   PerformWonders(i);
   }

const code FuncTableEntry FuncTable[2] =
   { f1, f2 };

void Dispatcher (void)
   {
   FuncTable(i);
   }

Dan: "... codify the function pointer array at the cost of an additional pushed return address."

Drew: "It's perhaps worth noting that a switch statement such as the one Dan posted generally compiles into a jump table anyway."

And when it compiles into a jump table, it does not cost an additional pushed return address.