Eval() in C?

[CapnKernel]

I basically want to be able to store a string in a struct and then be able to call that method when "the time is right." It's almost like Flash's event based structure, so I can't really have separate if statements for every string.

EDIT: mluckham, that'll probably work, thanks.

[Danny Diaz]

Originally Posted by CapnKernel

I basically want to be able to store a string in a struct and then be able to call that method when "the time is right."

Actually, what you're probably looking for is a "function pointer". Structs can store a pointer to a function call that you assign somewhere programmatically in code, and then when you want to call that function you just dereference the pointer (in a specific way). Check it out: http://www.newty.de/fpt/index.html

-Danny

[mluckham]

Pretty advanced (function pointers) but they are certainly useful as 'action routine pointers' in a state-action table (look up "Finite State Machine") provided the argument list to all the routines called is identical.

[AndrewN]

Originally Posted by CapnKernel

I basically want to be able to store a string in a struct and then be able to call that method when "the time is right." It's almost like Flash's event based structure, so I can't really have separate if statements for every string.

The way to do this in C is to do the command matching yourself and use function pointers to store a table of the functions you want to use.

The following code compiles with ANSI C. While running it waits for individual characters. If the character matches the command character 'cmd' then it de-references the function pointer, and calls the function. It passes no arguments onto the called function. (Hint: that's an exercise for you).

#include <stdlib.h>
#include <stdio.h>

// Four command functions. They must have identical arguments.

void go_left(void) { printf("Going Left\n"); }
void go_right(void) { printf("Going Right\n"); }
void stop(void) { printf("Stopped\n"); }
void quit(void) { printf("Bye\n"); exit(0); }

// An array of a two value structures.

struct {
    char cmd;			// The character
    void (*function)(void);	// a pointer to a function.
} commands[] = {
    {'l', &go_left},	// put the address of the function
    {'r', &go_right},	// into the function pointer
    {'s', &stop},
    {'q', &quit},
    {0, 0}		// marks the end of the array.
};

int
main(void) {
    char c; int i;

    while (1) {
        c = getchar();	// not available on FRC
        i = 0;
        while (commands[i].cmd) {
	    if (commands[i].cmd == c) {
		// dereference the pointer and call the function.
                // note the bracketing
		(*(commands[i].function))();
            }
	    i++;
        }
    }
}

You could obviously extend this to match whole strings instead of characters.

You do not have a "getchar()" function in the FRC code instead you'll have to read a character from one of the serial ports.

The above code is not pretty, badly commented, terse, and follows an arcane indenting style (I'm old).

You should use 'typedef' to define the structure instead of using it inline like this.

The structure is initialized after the command functions have been declared. If the command functions are in another file then you'll have to use 'extern' declarations of the functions before initializing the array.

A sample run:

$ cc ex1.c
$ ./a.out
l
Going Left
r
Going Right
q
Bye
$

[Salik Syed]

The only limitation is that your functions must take the same datatype. If you need them to take different data types you will need to make them all take a single void pointer to a block of memory then the function will need to reconstruct the data itself. This is probably too complicated and you probably won't need it. just throwing it out there if the need comes up

[Uberbots]

Originally Posted by Salik Syed

The only limitation is that your functions must take the same datatype. If you need them to take different data types you will need to make them all take a single void pointer to a block of memory then the function will need to reconstruct the data itself. This is probably too complicated and you probably won't need it. just throwing it out there if the need comes up

void pointers are evil... in a good way.

it is possible to create an eval function, using some derivative of a reverse polish notation format. however, for the purposes of robotics, it probably wont be worth it.